espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-09-10 14:59:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

tiny additions & fixes

Browse Source
This commit is contained in:
David MacKenzie
1993-09-03 22:47:04 +00:00
parent 81b407c990
commit 836a5ee449
1 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
ld/ld.texinfo
View File

@ -380,6 +380,7 @@ specified.
@cindex search directory, from cmd line @cindex search directory, from cmd line
@kindex -L@var{dir} @kindex -L@var{dir}
@item -L@var{searchdir} @item -L@var{searchdir}
@itemx -L @var{searchdir}
Add path @var{searchdir} to the list of paths that @code{ld} will search Add path @var{searchdir} to the list of paths that @code{ld} will search
for archive libraries and @code{ld} control scripts. You may use this for archive libraries and @code{ld} control scripts. You may use this
option any number of times. option any number of times.
@ -512,7 +513,8 @@ Omit all symbol information from the output file.
Normally, when @code{ld} places the global common symbols in the Normally, when @code{ld} places the global common symbols in the
appropriate output sections, it sorts them by size. First come all the appropriate output sections, it sorts them by size. First come all the
one byte symbols, then all the two bytes, then all the four bytes, and one byte symbols, then all the two bytes, then all the four bytes, and
then everything else. This option disables that sorting. then everything else. This is to prevent gaps between symbols due to
alignment constraints. This option disables that sorting.
@item -Tbss @var{org} @item -Tbss @var{org}
@kindex -Tbss @var{org} @kindex -Tbss @var{org}
@ -1404,7 +1406,7 @@ section names by either commas or whitespace.
@item * (@var{section}) @item * (@var{section})
@itemx * (@var{section}, @var{section}, @dots{}) @itemx * (@var{section}, @var{section}, @dots{})
@itemx * (@var{section} @var{section} @dots{} @itemx * (@var{section} @var{section} @dots{})
@cindex input sections to output section @cindex input sections to output section
@kindex *(@var{section}) @kindex *(@var{section})
Instead of explicitly naming particular input files in a link control Instead of explicitly naming particular input files in a link control
@ -1431,9 +1433,14 @@ SECTIONS @{
@} @}
@end example @end example
@samp{[ @var{section} @dots{} ]} used to be accepted as an alternate way
to specify named sections from all unallocated input files. Because
some operating systems (VMS) allow brackets in file names, that notation
is no longer supported.
@item @var{filename}@code{( COMMON )} @item @var{filename}@code{( COMMON )}
@itemx ( COMMON ) @itemx *( COMMON )
@kindex ( COMMON ) @kindex *( COMMON )
@cindex uninitialized data @cindex uninitialized data
@cindex commons in output @cindex commons in output
Specify where in your output file to place uninitialized data Specify where in your output file to place uninitialized data
@ -1445,11 +1452,6 @@ mechanisms for specifying where to place input-file sections:
@code{ld} permits you to refer to uninitialized data as if it @code{ld} permits you to refer to uninitialized data as if it
were in an input-file section named @code{COMMON}, regardless of the were in an input-file section named @code{COMMON}, regardless of the
input file's format. input file's format.
@samp{[ @var{section} @dots{} ]} used to be accepted as an alternate way
to specify named sections from all unallocated input files. Because
some operating systems (VMS) allow brackets in file names, this notation
is no longer supported.
@end table @end table
For example, the following command script arranges the output file into For example, the following command script arranges the output file into