From: Andrew Burgess Date: Tue, 14 Jul 2015 15:19:22 +0000 (+0100) Subject: ld/doc: Document that multiple MEMORY commands are allowed. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=127fcdff0541697ffd7169abafe5a51118bf65d0;p=binutils-gdb.git ld/doc: Document that multiple MEMORY commands are allowed. 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. --- diff --git a/ld/ChangeLog b/ld/ChangeLog index d1b819bc128..e0403295b47 100644 --- a/ld/ChangeLog +++ b/ld/ChangeLog @@ -1,3 +1,8 @@ +2015-08-03 Andrew Burgess + + * ld.texinfo (MEMORY): Explain that multiple MEMORY commands are + acceptable. + 2015-07-29 H.J. Lu * lexsup.c (parse_args): Don't set link_info.executable to diff --git a/ld/ld.texinfo b/ld/ld.texinfo index b48396d06bb..8a7a08f981e 100644 --- a/ld/ld.texinfo +++ b/ld/ld.texinfo @@ -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