aboutsummaryrefslogtreecommitdiff
path: root/ld/ld.texinfo
diff options
context:
space:
mode:
authorAlan Modra <amodra@gmail.com>2015-08-06 15:56:34 +0930
committerAlan Modra <amodra@gmail.com>2015-08-06 16:05:40 +0930
commite0a3af227ee0602ae69320fd6f931c363f14975b (patch)
tree4987f91beb70806b6267baa7fe3b6cb44a10bfb9 /ld/ld.texinfo
parent0cf003f49ee8bbd5dc5f1ce45193c7ae056c69b8 (diff)
downloadgdb-e0a3af227ee0602ae69320fd6f931c363f14975b.zip
gdb-e0a3af227ee0602ae69320fd6f931c363f14975b.tar.gz
gdb-e0a3af227ee0602ae69320fd6f931c363f14975b.tar.bz2
Revert ALIGN changes
Reverts a2c59f28 and e474ab13. Since the unary form of ALIGN only references "dot" implicitly, there isn't really a strong argument for making ALIGN use a relative value when inside an output section. * ldexp.c (align_dot_val): Delete. (fold_unary <ALIGN_K, NEXT>): Revert 2015-07-10 change. (is_align_conditional): Revert 2015-07-20 change. (exp_fold_tree_1): Likewise, but keep expanded comment. * scripttempl/elf.sc (.ldata, .bss): Revert 2015-07-20 change. * ld.texinfo (<ALIGN>): Correct description.
Diffstat (limited to 'ld/ld.texinfo')
-rw-r--r--ld/ld.texinfo2
1 files changed, 1 insertions, 1 deletions
diff --git a/ld/ld.texinfo b/ld/ld.texinfo
index bddf926..cf3b586 100644
--- a/ld/ld.texinfo
+++ b/ld/ld.texinfo
@@ -5992,7 +5992,7 @@ to the next @var{align} boundary. The single operand @code{ALIGN}
doesn't change the value of the location counter---it just does
arithmetic on it. The two operand @code{ALIGN} allows an arbitrary
expression to be aligned upwards (@code{ALIGN(@var{align})} is
-equivalent to @code{ALIGN(., @var{align})}).
+equivalent to @code{ALIGN(ABSOLUTE(.), @var{align})}).
Here is an example which aligns the output @code{.data} section to the
next @code{0x2000} byte boundary after the preceding section and sets a