aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorMatthieu Longo <matthieu.longo@arm.com>2025-09-12 17:26:38 +0100
committerMatthieu Longo <matthieu.longo@arm.com>2026-03-06 10:33:21 +0000
commitfe4a952931334dee80378c9f0606745976d8b30f (patch)
tree36342a13ff998c3129d966e3575b9702f02ab5c6 /include
parentb8ac7ad17b0299d91976fed3e660809225556b2b (diff)
downloadfsf-binutils-gdb-fe4a952931334dee80378c9f0606745976d8b30f.tar.gz
fsf-binutils-gdb-fe4a952931334dee80378c9f0606745976d8b30f.tar.bz2
fsf-binutils-gdb-fe4a952931334dee80378c9f0606745976d8b30f.zip
ld: clarify comments on /DISCARD/ output section behavior
The previous comments made it difficult to understand how the /DISCARD/ output section interacts with non-contiguous regions. In summary, the general rule is that the first (top-most) clause takes precedence over subsequent ones: - If /DISCARD/ appears first, the section is dropped. There is no need to warn about potential behavior changes with non-contiguous regions when the section is already discarded. - If /DISCARD/ follows clauses that assign the input section to an output section, /DISCARD/ is ignored. If the input section can't be assigned to the output section for a later reason, an error will be raised. Otherwise the input section will be assigned as intended to an output section specified by one of the matching clauses previous to /DISCARD/.
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions