Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

* ld.texinfo (MEMORY): Clarify use of >REGION.

Browse Source
This commit is contained in:
Ian Lance Taylor
1998-04-22 16:41:28 +00:00
parent bcb92b02a4
commit f8a86f8f3f
2 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ld/ChangeLog
View File

@@ -1,3 +1,7 @@
Wed Apr 22 12:40:56 1998 Ian Lance Taylor <ian@cygnus.com>
* ld.texinfo (MEMORY): Clarify use of >REGION.
Tue Apr 21 23:12:40 1998 Tom Tromey <tromey@scribbles.cygnus.com>
* Many files: Added gettext invocations around user-visible

17
ld/ld.texinfo
View File

@@ -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