From e4cf9ded94d1d28bcd39181b8a656329b7773b4a Mon Sep 17 00:00:00 2001 From: Dimitry Andric Date: Sat, 25 Feb 2017 14:40:58 +0000 Subject: Vendor import of lld release_40 branch r296202: https://llvm.org/svn/llvm-project/lld/branches/release_40@296202 --- docs/ReleaseNotes.rst | 23 ++++++++++------------- 1 file changed, 10 insertions(+), 13 deletions(-) diff --git a/docs/ReleaseNotes.rst b/docs/ReleaseNotes.rst index 6eb857070690..07fc7dd04e7f 100644 --- a/docs/ReleaseNotes.rst +++ b/docs/ReleaseNotes.rst @@ -5,9 +5,6 @@ LLD 4.0.0 Release Notes .. contents:: :local: -.. warning:: - These are in-progress notes for the upcoming LLVM 4.0.0 release. - Introduction ============ @@ -15,7 +12,7 @@ LLD is a linker which supports ELF (Unix), COFF (Windows) and Mach-O (macOS). It is generally faster than the GNU BFD/gold linkers or the MSVC linker. -LLD is designed to be a drop-in replacmenet for the system linkers, so +LLD is designed to be a drop-in replacement for the system linkers, so that users don't need to change their build systems other than swapping the linker command. @@ -49,17 +46,17 @@ Other notable changes are listed below: but the source location of unresolved symbols. * Error messages are printed in red just like Clang by default. You - can disable it by passing -no-color-diagnostics. + can disable it by passing ``-no-color-diagnostics``. * LLD's version string is now embedded in a .comment section in the result output file. You can dump it with this command: ``objdump -j -s .comment ``. -* The -Map option is supported. With that, you can print out section +* The ``-Map`` option is supported. With that, you can print out section and symbol information to a specified file. This feature is useful for analyzing link results. -* The file format for the -reproduce option has changed from cpio to +* The file format for the ``-reproduce`` option has changed from cpio to tar. * When creating a copy relocation for a symbol, LLD now scans the @@ -67,8 +64,8 @@ Other notable changes are listed below: space for the copy relocation is reserved in .bss.rel.ro instead of .bss. This fixes a security issue that read-only data in a DSO becomes writable if it is copied by a copy relocation. This issue - was disclosed originally on the binutils mailing list at - ``. + was disclosed originally on the + `binutils mailing list `_. * Compressed input sections are supported. @@ -76,7 +73,7 @@ Other notable changes are listed below: ``-Ttext``, ``-b binary``, ``-build-id=uuid``, ``-no-rosegment``, ``-nopie``, ``-nostdlib``, ``-omagic``, ``-retain-symbols-file``, ``-sort-section``, ``-z max-page-size`` and ``-z wxneeded`` are - suppoorted. + supported. * A lot of linker script directives have been added. @@ -84,15 +81,15 @@ Other notable changes are listed below: 0x200000 to make it huge-page friendly. * ARM port now supports GNU ifunc, the ARM C++ exceptions ABI, TLS - relocations and static linking. Problems with dlopen() on systems + relocations and static linking. Problems with ``dlopen()`` on systems using eglibc fixed. * MIPS port now supports input files in new R6 revision of MIPS ABIs or N32 ABI. Generated file now contains .MIPS.abiflags section and complete set of ELF headers flags. -* Relocations produced by the ``-mxgot`` compiler's flag is supported - for MIPS. Now it is possible to generate "large" GOT exceeds 64K +* Relocations produced by the ``-mxgot`` compiler flag is supported + for MIPS. Now it is possible to generate "large" GOT that exceeds the 64K limit. COFF Improvements -- cgit v1.2.3