[llvm-dev] when will LLD be included with LLVM releases?

[Sean Silva via llvm-dev]

I think that LLD is going to be included in the 4.0 release. At least,
we've been cherry-picking fixes into the release branch. I've CC'd some
others that will know the details.

Also, one thing to keep in mind is that the different platforms (ELF, COFF,
and MachO) are in different states of completeness, so depending on your
target platform (but not host platform!) you may have discrepancies.
Anecdotally, the ELF port is most actively developed/extensively tested
(builds significant fraction of all the packages in major open-source
package systems, self-hosts), followed by COFF (builds Chromium,
self-hosts), followed by MachO.

-- Sean Silva

On Fri, Feb 3, 2017 at 12:39 PM, Andrew Kelley via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> As a front end developer I would like to start experimenting with using
> LLD for a linker, especially because I could cross-compile without
> requiring the target's system linker being installed.
>
> However, currently it is not straightforward to depend on LLD, because it
> is not by default included in LLVM releases, and this means that it is
> absent from the various package managers. If users were to try my compiler,
> they would have to install LLVM, Clang, and LLD from source, which is a big
> thing for me to ask for.
>
> What I would like to see is LLD bundled with LLVM releases by default, or
> at least available independently such that it could build against an
> already-installed LLVM.
>
> What is the timeline for this?
>
> Regards,
> Andrew
>
> _______________________________________________
> 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/20170203/e77ffa03/attachment.html>