[llvm-branch-commits] [lld] r341913 - ReleaseNotes: fixes

[Ed Maste via llvm-branch-commits]

On 11 September 2018 at 04:05, Hans Wennborg via llvm-commits
<llvm-commits at lists.llvm.org> wrote:
> Author: hans
> Date: Tue Sep 11 01:05:44 2018
> New Revision: 341913
>
> URL: http://llvm.org/viewvc/llvm-project?rev=341913&view=rev
> Log:
> ReleaseNotes: fixes
>
> Modified:
>     lld/branches/release_70/docs/ReleaseNotes.rst
>
> Modified: lld/branches/release_70/docs/ReleaseNotes.rst
> URL: http://llvm.org/viewvc/llvm-project/lld/branches/release_70/docs/ReleaseNotes.rst?rev=341913&r1=341912&r2=341913&view=diff
> ==============================================================================
> --- lld/branches/release_70/docs/ReleaseNotes.rst (original)
> +++ lld/branches/release_70/docs/ReleaseNotes.rst Tue Sep 11 01:05:44 2018
> @@ -13,10 +13,10 @@ Mach-O (macOS), MinGW and WebAssembly. l
>  linkers and Microsoft link.exe, and is significantly faster than these system
>  default linkers.
>
> -lld 7.0 for ELF and COFF are production-ready. lld/ELF can build the entire
> +lld 7 for ELF and COFF are production-ready. lld/ELF can build the entire
>  FreeBSD/AMD64 and will be the default linker of the next version of the
>  operating system. lld/COFF is being used to build popular large programs such as

FWIW, in addition to amd64 (aka x86_64) FreeBSD is also using it as
the default linker for armv7, and it has been the default linker for
arm64 for some time. This is probably more detail than needed in
release notes, although it's a useful indication that lld is a viable
production quality linker on multiple CPU architectures.

(Also, we haven't fully switched i386 to lld just yet, because of some
outstanding breakage in the ports tree; there's a reasonable amount of
software that doesn't build with -fPIC or has non-PIC i386 assembly
and conflicts with lld's default of disallowing .text relocations.)