aboutsummaryrefslogtreecommitdiff
path: root/opcodes/cgen-bitset.c
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2016-09-20 10:49:39 +0100
committerAndrew Burgess <andrew.burgess@embecosm.com>2016-09-20 14:22:34 +0100
commita5bf7d4fe7a115a358528328b8d1ae221cd684fa (patch)
treeb69833ca19fcf5412f94992af9f62bce3601ed2f /opcodes/cgen-bitset.c
parent7d5adfe3118050243e85469ad891c7813e4db68a (diff)
downloadgdb-a5bf7d4fe7a115a358528328b8d1ae221cd684fa.zip
gdb-a5bf7d4fe7a115a358528328b8d1ae221cd684fa.tar.gz
gdb-a5bf7d4fe7a115a358528328b8d1ae221cd684fa.tar.bz2
ld: Extend documentation for EXCLUDE_FILE
There was a gap in the documentation of EXCLUDE_FILE that could cause confusion to a user. When writing an input section specifier like this: *(EXCLUDE_FILE (somefile.o) .text .text.*) this could mean one of the following: 1. All '.text' and '.text.*' from all files except for 'somefile.o', or 2. All '.text' from all files except 'somefile.o', and all '.text.*' sections from all files. It turns out that the second interpretation is correct, but the manual does not make this clear (to me at least). Hopefully this patch makes things clearer. ld/ChangeLog: * ld/ld.texinfo (Input Section Basics): Expand the description of EXCLUDE_FILE.
Diffstat (limited to 'opcodes/cgen-bitset.c')
0 files changed, 0 insertions, 0 deletions