problem with fill on IA64 linker
Eli Zaretskii
eliz@is.elta.co.il
Sun Feb 17 01:02:00 GMT 2002
More information about the Binutils mailing list
Sun Feb 17 01:02:00 GMT 2002
- Previous message (by thread): problem with fill on IA64 linker
- Next message (by thread): problem with fill on IA64 linker
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 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
- Previous message (by thread): problem with fill on IA64 linker
- Next message (by thread): problem with fill on IA64 linker
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list