OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

ld/doc: Document that multiple MEMORY commands are allowed.

Browse Source 
The linker documentation explicitly states that there can be only one
MEMORY command.  This is not true.  Multiple MEMORY commands are
allowed, the contents of all will be treated as if a single MEMORY
command was given.

Update the documentation to make this clear to the users.

ld/ChangeLog:

	* ld.texinfo (MEMORY): Explain that multiple MEMORY commands are
	acceptable.
This commit is contained in:
Andrew Burgess 2015-07-14 16:19:22 +01:00
parent 4122b41366
commit 127fcdff05
2 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ld/ChangeLog
View File

@ -1,3 +1,8 @@
2015-08-03 Andrew Burgess <andrew.burgess@embecosm.com>
* ld.texinfo (MEMORY): Explain that multiple MEMORY commands are
acceptable.
2015-07-29 H.J. Lu <hongjiu.lu@intel.com>
* lexsup.c (parse_args): Don't set link_info.executable to

7
ld/ld.texinfo
View File

@ -4970,9 +4970,10 @@ set section addresses based on the memory regions, and will warn about
regions that become too full. The linker will not shuffle sections
around to fit into the available regions.
A linker script may contain at most one use of the @code{MEMORY}
command. However, you can define as many blocks of memory within it as
you wish. The syntax is:
A linker script may contain many uses of the @code{MEMORY} command,
however, all memory blocks defined are treated as if they were
specified inside a single @code{MEMORY} command. The syntax for
@code{MEMORY} is:
@smallexample
@group
MEMORY