This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
[PING] Re: [PATCH] ld/doc: Document that multiple MEMORY commands are allowed.
- From: Andrew Burgess <andrew dot burgess at embecosm dot com>
- To: binutils at sourceware dot org
- Date: Mon, 3 Aug 2015 16:59:04 +0100
- Subject: [PING] Re: [PATCH] ld/doc: Document that multiple MEMORY commands are allowed.
- Authentication-results: sourceware.org; auth=none
- References: <1436887746-19501-1-git-send-email-andrew dot burgess at embecosm dot com>
Ping.
Thanks,
Andrew
* Andrew Burgess <andrew.burgess@embecosm.com> [2015-07-14 16:29:06 +0100]:
> 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.
>
> ---
>
> I'm not convinced that I've got the best wording for the new
> documentation, so any suggestions for improvements are appreciated.
>
> Thanks,
> Andrew
>
> ---
>
>
> ld/ChangeLog:
>
> * ld.texinfo (MEMORY): Explain that multiple MEMORY commands are
> acceptable.
> ---
> ld/ChangeLog | 5 +++++
> ld/ld.texinfo | 7 ++++---
> 2 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/ld/ChangeLog b/ld/ChangeLog
> index 3035fd7..199c160 100644
> --- a/ld/ChangeLog
> +++ b/ld/ChangeLog
> @@ -1,3 +1,8 @@
> +2015-07-14 Andrew Burgess <andrew.burgess@embecosm.com>
> +
> + * ld.texinfo (MEMORY): Explain that multiple MEMORY commands are
> + acceptable.
> +
> 2015-07-14 Nick Clifton <nickc@redhat.com>
>
> * ld.texinfo (Options): Add missing period after @xref.
> diff --git a/ld/ld.texinfo b/ld/ld.texinfo
> index e7989b7..d819ad4 100644
> --- a/ld/ld.texinfo
> +++ b/ld/ld.texinfo
> @@ -4969,9 +4969,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
> --
> 2.4.0
>