FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ld: More documentation for --defsym

Browse source 
The ordering of command line options --defsym and -T is important,
however, the description of --defsym in the manual doesn't mention
this.

This commit adds more text to the description of --defsym to try and
explain this ordering requirement.

ld/ChangeLog:

	* ld.texi (Options): Extend the description of --defsym.
This commit is contained in:
Andrew Burgess 2020-10-06 15:30:15 +01:00
parent 6915020bb1
commit 54874444da
2 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
ld/ChangeLog
View file

@ -1,3 +1,7 @@
2020-10-16 Andrew Burgess <andrew.burgess@embecosm.com>
* ld.texi (Options): Extend the description of --defsym.
2020-10-16 Nick Clifton <nickc@redhat.com>
PR 26626

9
ld/ld.texi
View file

@ -1705,6 +1705,15 @@ using the linker command language from a script (@pxref{Assignments}).
@emph{Note:} there should be no white space between @var{symbol}, the
equals sign (``@key{=}''), and @var{expression}.
The linker processes @samp{--defsym} arguments and @samp{-T} arguments
in order, placing @samp{--defsym} before @samp{-T} will define the
symbol before the linker script from @samp{-T} is processed, while
placing @samp{--defsym} after @samp{-T} will define the symbol after
the linker script has been processed. This difference has
consequences for expressions within the linker script that use the
@samp{--defsym} symbols, which order is correct will depend on what
you are trying to achieve.
@cindex demangling, from command line
@kindex --demangle[=@var{style}]
@kindex --no-demangle