public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Alexander Fedotov <alfedotov@gmail.com>
Cc: Nick Clifton <nickc@redhat.com>, binutils <binutils@sourceware.org>
Subject: Re: [PATCH] Add support for non-contiguous memory regions
Date: Wed, 3 Jun 2020 14:48:54 +0200	[thread overview]
Message-ID: <CAKdteOZ0K4zSmbKF0X0PSGPE0PLN2cKAqVWXJg3AJs4DajzUJQ@mail.gmail.com> (raw)
In-Reply-To: <CAN8C2CqT8frDDMrEjpS7PzhdO8bRVvJm5TiZpiw+ijMff_NS5A@mail.gmail.com>

On Tue, 2 Jun 2020 at 14:49, Alexander Fedotov <alfedotov@gmail.com> wrote:
>
> Hello Christophe
>
> I found it very useful feature.

Thanks for the positive feedback, that's good to read.

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

I think this was discussed in the original thread, eg
https://sourceware.org/legacy-ml/binutils/2017-02/msg00250.html and
https://sourceware.org/legacy-ml/binutils/2017-03/msg00020.html

I would look nice indeed, I just fear unexpected complications since
this modifies the linker script language.

Maybe some main maintainers have thoughts on the difficulty and risks
of implementing this? Nick?

Thanks,

Christophe

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

      reply	other threads:[~2020-06-03 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
2020-06-03 12:48                           ` Christophe Lyon [this message]

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=CAKdteOZ0K4zSmbKF0X0PSGPE0PLN2cKAqVWXJg3AJs4DajzUJQ@mail.gmail.com \
    --to=christophe.lyon@linaro.org \
    --cc=alfedotov@gmail.com \
    --cc=binutils@sourceware.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).