This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: problem with fill on IA64 linker
- From: Eli Zaretskii <eliz at is dot elta dot co dot il>
- To: amodra at bigpond dot net dot au
- Cc: geoff dot lowney at intel dot com, bug-binutils at gnu dot org, binutils at sources dot redhat dot com, robert dot muth at intel dot com
- Date: Sun, 17 Feb 2002 11:01:06 +0200 (IST)
- Subject: Re: problem with fill on IA64 linker
- References: <29AD895CE780D511A8870002A50A666D015F37B6@hdsmsx106.hd.intel.com> <20020215001108.GR12764@bubble.sa.bigpond.net.au> <20020215020614.GT12764@bubble.sa.bigpond.net.au> <20020215033352.GU12764@bubble.sa.bigpond.net.au>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> From: Alan Modra <amodra@bigpond.net.au>
> Date: Fri, 15 Feb 2002 14:03:52 +1030
>
> +precedence. See (@pxref{Output Section Fill}) for details on the fill
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That should have been just "@xref{Output Section Fill}," without "See"
and without the parens. @xref generates "See" automatically, whereas
the parentheses look mighty awkward in this context.
> +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
> +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
> +pattern is the four least significant bytes of the value of the
> +expression. In all cases, the number is big-endian.
This will look much nicer in the printed manual if you use markup
instead of the ASCII art: @samp{0x} instead of "0x", @code{+} instead
of '+', etc.
HTH