From: Ian Lance Taylor Date: Wed, 22 Apr 1998 16:41:28 +0000 (+0000) Subject: * ld.texinfo (MEMORY): Clarify use of >REGION. X-Git-Tag: gdb-4_18~2526 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f8a86f8f3f97e848b22fdb79e9b32a3dbf5e1d78;p=external%2Fbinutils.git * ld.texinfo (MEMORY): Clarify use of >REGION. --- diff --git a/ld/ChangeLog b/ld/ChangeLog index 1113fea..c24c6bd 100644 --- a/ld/ChangeLog +++ b/ld/ChangeLog @@ -1,3 +1,7 @@ +Wed Apr 22 12:40:56 1998 Ian Lance Taylor + + * ld.texinfo (MEMORY): Clarify use of >REGION. + Tue Apr 21 23:12:40 1998 Tom Tromey * Many files: Added gettext invocations around user-visible diff --git a/ld/ld.texinfo b/ld/ld.texinfo index 98e6602..ddcba35 100644 --- a/ld/ld.texinfo +++ b/ld/ld.texinfo @@ -2708,14 +2708,15 @@ MEMORY @end group @end smallexample -If you have defined a memory region named @samp{mem}, you can direct the -linker to place specific output sections into that memory region by -using the @samp{>@var{region}} output section attribute. @xref{Output -Section Region}. If no address was specified for the output section, -the linker will set the address to the next available address within the -memory region. If the combined output sections directed to a memory -region are too large for the region, the linker will issue an error -message. +Once you define a memory region, you can direct the linker to place +specific output sections into that memory region by using the +@samp{>@var{region}} output section attribute. For example, if you have +a memory region named @samp{mem}, you would use @samp{>mem} in the +output section definition. @xref{Output Section Region}. If no address +was specified for the output section, the linker will set the address to +the next available address within the memory region. If the combined +output sections directed to a memory region are too large for the +region, the linker will issue an error message. @node PHDRS @section PHDRS Command