From 9673c93c263a7f60dd1cf8ff72530239f97a2fa8 Mon Sep 17 00:00:00 2001 From: Alan Modra Date: Sun, 17 Feb 2002 22:15:40 +0000 Subject: [PATCH] * ld.texinfo (Output Section Fill): Fix amateur texinfo. (FILL): Likewise. --- ld/ChangeLog | 5 +++++ ld/ld.texinfo | 10 +++++----- 2 files changed, 10 insertions(+), 5 deletions(-) diff --git a/ld/ChangeLog b/ld/ChangeLog index 089f441..79d7449 100644 --- a/ld/ChangeLog +++ b/ld/ChangeLog @@ -1,3 +1,8 @@ +2002-02-18 Alan Modra + + * ld.texinfo (Output Section Fill): Fix amateur texinfo. + (FILL): Likewise. + 2002-02-17 Hans-Peter Nilsson * emultempl/mmo.em (mmo_after_open): Don't call diff --git a/ld/ld.texinfo b/ld/ld.texinfo index 4addc3f..3292bc8 100644 --- a/ld/ld.texinfo +++ b/ld/ld.texinfo @@ -2943,10 +2943,10 @@ FILL(0x90909090) @end smallexample The @code{FILL} command is similar to the @samp{=@var{fillexp}} output -section attribute (@pxref{Output Section Fill}), but it only affects the +section attribute, but it only affects the part of the section following the @code{FILL} command, rather than the entire section. If both are used, the @code{FILL} command takes -precedence. See (@pxref{Output Section Fill}) for details on the fill +precedence. @xref{Output Section Fill}, for details on the fill expression. @node Output Section Keywords @@ -3228,15 +3228,15 @@ You can set the fill pattern for an entire section by using within the output section (for example, gaps left due to the required alignment of input sections) will be filled with the value, repeated as necessary. If the fill expression is a simple hex number, ie. a string -of hex digit starting with "0x" and without a trailing "k" or "M", then +of hex digit starting with @samp{0x} and without a trailing @samp{k} or @samp{M}, then an arbitrarily long sequence of hex digits can be used to specify the fill pattern; Leading zeros become part of the pattern too. For all -other cases, including extra parentheses or a unary '+', the fill +other cases, including extra parentheses or a unary @code{+}, the fill pattern is the four least significant bytes of the value of the expression. In all cases, the number is big-endian. You can also change the fill value with a @code{FILL} command in the -output section commands; see @ref{Output Section Data}. +output section commands; (@pxref{Output Section Data}). Here is a simple example: @smallexample -- 2.7.4