summaryrefslogtreecommitdiff
path: root/ld/ld.texinfo
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2013-04-30 12:52:58 +0000
committerNick Clifton <nickc@redhat.com>2013-04-30 12:52:58 +0000
commit25066f02ffc58b163b4c6716b5ed9f1aa707bd58 (patch)
tree2cc589de8f1222ecc2604fd9ff45c8a06eda864f /ld/ld.texinfo
parentb78042ae9dab42b1b3700e8f2f83f54e3a2ea4fb (diff)
downloadbinutils-redhat-25066f02ffc58b163b4c6716b5ed9f1aa707bd58.tar.gz
* ld.texinfo (SORT_BY_ALIGNMENT): Fix and clarify typo - sections
are sorted by descending order of alignment.
Diffstat (limited to 'ld/ld.texinfo')
-rw-r--r--ld/ld.texinfo6
1 files changed, 3 insertions, 3 deletions
diff --git a/ld/ld.texinfo b/ld/ld.texinfo
index 79591c7f7f..48ae4bf8ca 100644
--- a/ld/ld.texinfo
+++ b/ld/ld.texinfo
@@ -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