[llvm-dev] [cfe-dev] LLD to be the default linker in Clang

Rui Ueyama via llvm-dev llvm-dev at lists.llvm.org
Fri Oct 28 10:53:24 PDT 2016


On Fri, Oct 28, 2016 at 10:38 AM, Renato Golin via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On 28 October 2016 at 18:12, Ed Maste <emaste at freebsd.org> wrote:
> > It should be possible to search the path for ld.lld first, then ld,
> > but to me it seems like it will just be more confusing.
>
> Hum, for me it would be less confusing. :)
>
> GCC uses bfd by default, LLVM uses LLD. If you want to change, use
> -fuse-ld.
>
> What would be confusing in this scenario?
>

In practice, I think your proposal can be read for most people as a
proposal to do dogfooding LLD more widely in LLVM by making it the default
linker. I've been using LLD as default for a long period of time (probably
a year) and saw no problem. So it should be doable. Do people okay with
that? Probably, as long as it works, no one would really care, maybe?


>
> > Clang's current approach (ld from $PATH by default, or ld.arg from
> > -fuse-ld=arg) suits us in FreeBSD. Today we have:
> >     /usr/bin/ld.bfd (GNU ld 2.17.50)
> >     /usr/bin/ld (ld.bfd symlink)
> >
> > We'll soon add
> >     /usr/bin/ld.lld
>
> This seems like a simple enough approach. I guess my problem is more
> about building toolchains than shipping them.
>
>
> > The only downside of -fuse-ld= that I'm aware of affects GCC only, not
> > Clang: GCC accepts only -fuse-ld=bfd and -fuse-ld=gold, and Davide's
> > patch to add -fuse-ld=lld was met with hostility. But that shouldn't
> > have any effect on Clang.
>
> Just had a look at the thread. Some silly comments were expected, but
> I think Davide has withdrawn his patch too early.
>
> AFAIK, there's absolutely nothing in the GCC license, moto and
> copyright statements that forbid the usage of a non-GNU linker, and
> the argument "lld has bugs" is pointless.
>
> I would try again.
>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161028/783a6350/attachment.html>


More information about the llvm-dev mailing list