OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* ld.texinfo (SORT_BY_ALIGNMENT): Fix and clarify typo - sections 

are sorted by descending order of alignment.
This commit is contained in:
Nick Clifton 2013-04-30 12:52:58 +00:00
parent 2cc10f5b85
commit 1ae5c3ae9b
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ld/ChangeLog
View File

@ -1,3 +1,8 @@
2013-04-30 Nick Clifton <nickc@redhat.com>
* ld.texinfo (SORT_BY_ALIGNMENT): Fix and clarify typo - sections
are sorted by descending order of alignment.
2013-04-29 Nick Clifton <nickc@redhat.com>
* scripttempl/DWARF.sc: Add support for .debug_line.* and

6
ld/ld.texinfo
View File

@ -4031,7 +4031,7 @@ into ascending order by name before placing them in the output file.
@cindex SORT_BY_ALIGNMENT
@code{SORT_BY_ALIGNMENT} is very similar to @code{SORT_BY_NAME}. The
difference is @code{SORT_BY_ALIGNMENT} will sort sections into
ascending order by alignment before placing them in the output file.
descending order by alignment before placing them in the output file.
@cindex SORT_BY_INIT_PRIORITY
@code{SORT_BY_INIT_PRIORITY} is very similar to @code{SORT_BY_NAME}. The
@ -4048,11 +4048,11 @@ can be at most 1 level of nesting for section sorting commands.
@enumerate
@item
@code{SORT_BY_NAME} (@code{SORT_BY_ALIGNMENT} (wildcard section pattern)).
It will sort the input sections by name first, then by alignment if 2
It will sort the input sections by name first, then by alignment if two
sections have the same name.
@item
@code{SORT_BY_ALIGNMENT} (@code{SORT_BY_NAME} (wildcard section pattern)).
It will sort the input sections by alignment first, then by name if 2
It will sort the input sections by alignment first, then by name if two
sections have the same alignment.
@item
@code{SORT_BY_NAME} (@code{SORT_BY_NAME} (wildcard section pattern)) is