From: Alexander Fedotov <alfedotov@gmail.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Nick Clifton <nickc@redhat.com>, binutils <binutils@sourceware.org>
Subject: Re: [PATCH] Add support for non-contiguous memory regions
Date: Tue, 2 Jun 2020 15:49:44 +0300 [thread overview]
Message-ID: <CAN8C2CqT8frDDMrEjpS7PzhdO8bRVvJm5TiZpiw+ijMff_NS5A@mail.gmail.com> (raw)
In-Reply-To: <CAKdteOZN5OS44f0Od0ZSb2Jiw34FX5b--5ku-U5asSi=vJFV=g@mail.gmail.com>
Hello Christophe
I found it very useful feature.
But I'm just curious if it is possible to extend linker syntax to support
syntax with output regions separated by OR :
text : { *(.text*) } > REGION0 | REGION1 | REGION2
It is more convenient in some cases. For example CMSIS has linker script
like this:
.text :
{
KEEP(*(.vectors))
*(.text*)
KEEP(*(.init))
KEEP(*(.fini))
/* .ctors */
*crtbegin.o(.ctors)
*crtbegin?.o(.ctors)
*(EXCLUDE_FILE(*crtend?.o *crtend.o) .ctors)
*(SORT(.ctors.*))
*(.ctors)
/* .dtors */
*crtbegin.o(.dtors)
*crtbegin?.o(.dtors)
*(EXCLUDE_FILE(*crtend?.o *crtend.o) .dtors)
*(SORT(.dtors.*))
*(.dtors)
*(.rodata*)
KEEP(*(.eh_frame*))
} > FLASH
So that we have to duplicate this rather than use | in output regions.
What do you think?
Alex
On Fri, Mar 13, 2020 at 5:46 PM Christophe Lyon via Binutils <
binutils@sourceware.org> wrote:
> On Fri, 13 Mar 2020 at 15:21, Nick Clifton <nickc@redhat.com> wrote:
> >
> > Hi Christophe,
> >
> > > Ping?
> > >
> > > https://sourceware.org/pipermail/binutils/2020-February/109942.html
> >
> > Oops - sorry - the patch is good. Approved - please apply.
> >
>
> Thanks!
> Pushed as abf874aafe3d717573e4a48bf0e3c6334e666a55
>
> Christophe
>
> > Cheers
> > Nick
> >
>
next prev parent reply other threads:[~2020-06-02 12:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 12:34 Christophe Lyon
2020-02-14 13:02 ` Tamar Christina
2020-02-14 13:54 ` Christophe Lyon
2020-02-19 7:19 ` Alan Modra
2020-02-19 12:28 ` Christophe Lyon
2020-02-19 22:23 ` Alan Modra
2020-02-20 4:37 ` Christophe Lyon
2020-02-20 8:15 ` Alan Modra
2020-02-20 9:00 ` Christophe Lyon
2020-02-28 17:31 ` Christophe Lyon
2020-03-09 13:10 ` Christophe Lyon
2020-03-13 14:21 ` Nick Clifton
2020-03-13 14:46 ` Christophe Lyon
2020-06-02 12:49 ` Alexander Fedotov [this message]
2020-06-03 12:48 ` Christophe Lyon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN8C2CqT8frDDMrEjpS7PzhdO8bRVvJm5TiZpiw+ijMff_NS5A@mail.gmail.com \
--to=alfedotov@gmail.com \
--cc=binutils@sourceware.org \
--cc=christophe.lyon@linaro.org \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).