intel/llvm
1
0
Fork 0
mirror of https://github.com/intel/llvm.git synced 2026-01-23 07:58:23 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
c24f66e33bcbc82e40f5dd94cda12430dc819638
llvm/lld/docs/ReleaseNotes.rst

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

60 lines
1.7 KiB
ReStructuredText
Raw Normal View History

[LLVM][utils] Add script which clears release notes (#153593) The script copies `ReleaseNotesTemplate.txt` to corresponding `ReleaseNotes.rst`/`.md` to clear release notes. The suffix of `ReleaseNotesTemplate.txt` must be `.txt`. If it is `.rst`/`.md`, it will be treated as a documentation source file when building documentation.
2025-08-15 19:00:08 +08:00
.. If you want to modify sections/contents permanently, you should modify both
ReleaseNotes.rst and ReleaseNotesTemplate.txt.
[docs] Remove hard-coded version numbers from sphinx configs This updates all the non-runtime project release notes to use the version number from CMake instead of the hard-coded version numbers in conf.py. It also hides warnings about pre-releases when the git suffix is dropped from the LLVM version in CMake. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D112181
2022-02-01 23:13:01 -08:00
===========================
lld |release| Release Notes
===========================
Start adding release notes for lld. llvm-svn: 260960
2016-02-16 13:12:55 +00:00
.. contents::
:local:
[docs] Remove hard-coded version numbers from sphinx configs This updates all the non-runtime project release notes to use the version number from CMake instead of the hard-coded version numbers in conf.py. It also hides warnings about pre-releases when the git suffix is dropped from the LLVM version in CMake. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D112181
2022-02-01 23:13:01 -08:00
.. only:: PreRelease
.. warning::
These are in-progress notes for the upcoming LLVM |release| release.
Release notes for previous releases can be found on
`the Download Page <https://releases.llvm.org/download.html>`_.
Start adding release notes for lld. llvm-svn: 260960
2016-02-16 13:12:55 +00:00
Introduction
============
[docs] Remove hard-coded version numbers from sphinx configs This updates all the non-runtime project release notes to use the version number from CMake instead of the hard-coded version numbers in conf.py. It also hides warnings about pre-releases when the git suffix is dropped from the LLVM version in CMake. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D112181
2022-02-01 23:13:01 -08:00
This document contains the release notes for the lld linker, release |release|.
ReleaseNotes: user lower-case for lld in the text llvm-svn: 325869
2018-02-23 08:27:38 +00:00
Here we describe the status of lld, including major improvements
from the previous release. All lld releases may be downloaded
ReleaseNotes: update links to use https llvm-svn: 341788
2018-09-10 08:52:31 +00:00
from the `LLVM releases web site <https://llvm.org/releases/>`_.
Start adding release notes for lld. llvm-svn: 260960
2016-02-16 13:12:55 +00:00
Non-comprehensive list of changes in this release
=================================================
ELF Improvements
----------------
[lld][ELF] Add --why-live flag (inspired by Mach-O) (#127112) This prints a stack of reasons that symbols that match the given glob(s) survived GC. It has no effect unless section GC occurs. This implementation does not require -ffunction-sections or -fdata-sections to produce readable results, althought it does tend to work better (as does GC). Details about the semantics: - Some chain of liveness reasons is reported; it isn't specified which chain. - A symbol or section may be live: - Intrisically (e.g., entry point) - Because needed by a live symbol or section - (Symbols only) Because part of a section live for another reason - (Sections only) Because they contain a live symbol - Both global and local symbols (`STB_LOCAL`) are supported. - References to symbol + offset are considered to point to: - If the referenced symbol is a section (`STT_SECTION`): - If a sized symbol encloses the referenced offset, the enclosing symbol. - Otherwise, the section itself, generically. - Otherwise, the referenced symbol.
2025-03-26 09:56:33 -07:00
[ELF] Add --print-gc-sections=<file> (#159706) Add `--print-gc-sections=<file>` to redirect garbage collection section listing to a file, avoiding contamination of stdout with other linker output. mold has recently added the option. GNU ld feature request: https://sourceware.org/bugzilla/show_bug.cgi?id=33331
2025-09-19 09:22:37 -07:00
* ``--print-gc-sections=<file>`` prints garbage collection section listing to a file.
(`#159706 <https://github.com/llvm/llvm-project/pull/159706>`_)
[ELF] Add convenience TableGen classes to enforce two dashes for options not supported by GNU ld Announced on https://lists.llvm.org/pipermail/llvm-dev/2020-May/141416.html For many options, we have to support either one or two dash to be compatible with GNU ld. For newer and lld specific options, we can enforce strict double dashes. Affected options: * --thinlto-* * --lto-* * --shuffle-sections= This patch does not change `-plugin-opt=*` because clang driver passes `-plugin-opt=*` and I don't intend to cause churn. In 2000, GNU ld tried something similar with --omagic https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4897a3288f37d5f69e8acd256a6e83e607fe8d8 Reviewed By: tejohnson, psmith Differential Revision: https://reviews.llvm.org/D79371
2020-05-04 14:42:36 -07:00
Breaking changes
----------------
[ELF] Error if a section address is smaller than image base When using `-no-pie` without a `SECTIONS` command, the linker uses the target's default image base. If `-Ttext=` or `--section-start` specifies an output section address below this base, the result is likely unintended. - With `--no-rosegment`, the PT_LOAD segment covering the ELF header cannot include `.text` if `.text`'s address is too low, causing an `error: output file too large`. - With default `--rosegment`: - If a read-only section (e.g., `.rodata`) exists, a similar `error: output file too large` occurs. - Without read-only sections, the PT_LOAD segment covering the ELF header and program headers includes no sections, which is unusual and likely undesired. This also causes non-ascending PT_LOAD `p_vaddr` values related to the PT_LOAD that overlaps with PT_PHDR (#138584). To prevent these issues, report an error if a section address is below the image base and suggest `--image-base`. This check also applies when `--image-base` is explicitly set but is skipped when a `SECTIONS` command is used. Pull Request: https://github.com/llvm/llvm-project/pull/140187
2025-05-21 09:19:47 -07:00
Start adding release notes for lld. llvm-svn: 260960
2016-02-16 13:12:55 +00:00
COFF Improvements
-----------------
[docs] Mention some notable feature in the release notes Differential Revision: https://reviews.llvm.org/D52908 llvm-svn: 343878
2018-10-05 19:43:20 +00:00
MinGW Improvements
------------------
Start adding release notes for lld. llvm-svn: 260960
2016-02-16 13:12:55 +00:00
MachO Improvements
------------------
[lld][macho][NFC] Add release note for #158720 (#161295) I forgot to add a release note for https://github.com/llvm/llvm-project/pull/158720 so I'll add it here.
2025-09-29 16:28:40 -07:00
* ``--separate-cstring-literal-sections`` emits cstring literal sections into sections defined by their section name.
(`#158720 <https://github.com/llvm/llvm-project/pull/158720>`_)
[lld][MachO] Tail merge strings (#161262) Add the flag `--tail-merge-strings` to enable tail merging of cstrings. For example, if we have strings `mystring\0` and `ring\0`, we could place `mystring\0` at address `0x1000` and `ring\0` at address `0x1004` and have them share the same underlying data. It turns out that many ObjC method names can be tail merged. For example, `error:` and `doFoo:error:`. On a large iOS binary, we saw nearly a 15% size improvement in the `__TEXT__objc_methname` section and negligible impact on link time. ``` $ bloaty --domain=vm merged.o.stripped -- base.o.stripped VM SIZE -------------- +95% +5.85Ki [__TEXT] -2.4% -239Ki __TEXT,__cstring -14.5% -710Ki __TEXT,__objc_methname -1.0% -944Ki TOTAL ``` Tail merging for MachO was originally removed in https://github.com/llvm/llvm-project/commit/7c269db779ff3950bac2e25ea78b14b4e2b8b247. The previous implementation used `StringTableBuilder`, but that was removed in https://github.com/llvm/llvm-project/commit/4308f031cd0c679c539914608134b9c8046743b3 to ensure deduplicated strings are aligned correctly. This implementation ensures that tail merged strings are also aligned correctly. Special thanks to nocchijiang for pointing this out in https://github.com/llvm/llvm-project/pull/158720#issuecomment-3310416030. Depends on https://github.com/llvm/llvm-project/pull/161253.
2025-10-03 09:38:10 -07:00
* ``--tail-merge-strings`` enables tail merging of cstring literals.
(`#161262 <https://github.com/llvm/llvm-project/pull/161262>`_)
[lld][macho][NFC] Add release note for #158720 (#161295) I forgot to add a release note for https://github.com/llvm/llvm-project/pull/158720 so I'll add it here.
2025-09-29 16:28:40 -07:00
[WebAssembly] Initial support for shared objects (-shared) Based on the initial spec proposal: https://github.com/WebAssembly/tool-conventions/blob/master/DynamicLinking.md The llvm/codegen side of this is still missing but I believe this change is still worth landing as an incremental step Differential Revision: https://reviews.llvm.org/D54249 llvm-svn: 346918
2018-11-15 00:37:21 +00:00
WebAssembly Improvements
------------------------
[lld][WebAssembly] Default to --stack-first (#166998) The really painful part of this PR was updating all the test files. I had some help from Gemini GLI there which did a pretty good job (got maybe 80% of the updates done). Fixes: #151015
2025-11-07 16:27:06 -08:00
* The ``--stack-first`` flag is now enabled by default. The old
behavior can be enabled using ``--no-stack-first``.
[LLD][ARM] Handle .ARM.exidx sections at non-zero output sec offset Embedded systems that do not use an ELF loader locate the .ARM.exidx exception table via linker defined __exidx_start and __exidx_end rather than use the PT_ARM_EXIDX program header. This means that some linker scripts such as the picolibc C library's linker script, do not have the .ARM.exidx sections at offset 0 in the OutputSection. For example: .except_unordered : { . = ALIGN(8); PROVIDE(__exidx_start = .); *(.ARM.exidx*) PROVIDE(__exidx_end = .); } >flash AT>flash :text This is within the specification of Arm exception tables, and is handled correctly by ld.bfd. This patch has 2 parts. The first updates the writing of the data of the .ARM.exidx SyntheticSection to account for a non-zero OutputSection offset. The second part makes the PT_ARM_EXIDX program header generation a special case so that it covers only the SyntheticSection and not the parent OutputSection. While not strictly necessary for programs locating the exception tables via the symbols it may cause ELF utilities that locate the exception tables via the PT_ARM_EXIDX program header to fail. This does not seem to be the case for GNU and LLVM readelf which seems to look for the SHT_ARM_EXIDX section. Differential Revision: https://reviews.llvm.org/D148033
2023-04-11 18:14:40 +01:00
Fixes
#####
Reference in New Issue Copy Permalink