<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - -fuse-ld on unknown triple uses gcc instead of gnutools"
href="https://bugs.llvm.org/show_bug.cgi?id=42503">42503</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>-fuse-ld on unknown triple uses gcc instead of gnutools
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>-New Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>drdeeglaze@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>htmldeveloper@gmail.com, llvm-bugs@lists.llvm.org, neeilans@live.com, richard-llvm@metafoo.co.uk
</td>
</tr></table>
<p>
<div>
<pre>Not sure if feature request or bug, but..
I'm switching our GCC-based toolchain for the Asylo project (<a href="https://asylo.dev">https://asylo.dev</a>)
over to clang, and have been trying to avoid modifying clang in the process.
Asylo is kind of link a different OS from existing OSes, but is POSIX-based, so
very similar to Linux. Our current backends target x86_64, so I've chosen the
target triple x86_64-newlib-asylo-gnu.
Since asylo is an unknown OS, the toolchain defaults to Generic_GCC. Everything
compiles just fine with clang, but the linker fails trying to run gcc to
complete the link command. I pass in -fuse-ld=lld, but this is not relevant to
the command issued in ToolChains/Gnu.cpp.
If providing -fuse-ld were to drive gnutools::Linker-like behavior, would that
be a dramatic semantic change, or would it be a reasonable improvement? At this
point, I have a tiny Asylo subclass of Generic_GCC that does nothing but return
a gnutools::Linker for buildLinker in order to make local progress. This feels
too heavy-handed for just choosing a linker without a gcc fallback though.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>