public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Alan Modra <amodra@gmail.com>
Cc: hjl.tools@gmail.com, binutils@sourceware.org, siddhesh@redhat.com
Subject: Re: RFC: ld: Add --text-section-ordering-file (version 2)
Date: Thu, 2 May 2024 16:16:56 +0100	[thread overview]
Message-ID: <c234e674-fe64-4b01-b9ad-afd8c65c46e0@redhat.com> (raw)
In-Reply-To: <Zi7l6irHuTIDwH8i@squeak.grove.modra.org>

Hi Alan,

> The patch wasn't too far wrong.  I had some compile issues when plugin
> support was disabled, and it is probably a bad idea to allow creation
> of new output sections via --section-ordering-file, so that is now
> disallowed.

Thanks for creating this.  I am playing with it at the moment.

> I'm not putting forward this patch as a finished work, it's just a
> demonstrator.
> 
> What I'd like to see is:
> 1) Lose that horrible "INCLUDE section-ordering-file" requirement for
>     existing scripts.  Do you really want that put into every output
>     section in every script in scripttempl/?

No, and removing the need to do this is definitely a good thing.

> 2) Parse the section ordering file in ldgram.y.  An entry under file:
>     would be appropriate, like we do for version scripts.  That would
>     at least lose the SECTIONS clause required by my demonstrator
>     patch.  You wouldn't necessarily need to follow existing
>     specification of output and input sections, or to support other
>     things allowed in output sections, but I do think a syntax with an
>     explicit output section is a good idea.  ie. not one where the
>     output .text is deduced from the input .text.mumble.

Hmm, OK, I will look into this.

Cheers
   Nick


  reply	other threads:[~2024-05-02 15:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 13:01 Nick Clifton
2024-04-25 15:32 ` H.J. Lu
2024-04-26  9:38   ` Nick Clifton
2024-04-26  1:46 ` Hans-Peter Nilsson
2024-04-26  9:46   ` Nick Clifton
2024-04-27  0:46     ` Hans-Peter Nilsson
2024-04-26  4:17 ` Alan Modra
2024-04-26  9:59   ` Nick Clifton
2024-04-26 12:43     ` Alan Modra
2024-04-29  0:12       ` Alan Modra
2024-05-02 15:16         ` Nick Clifton [this message]
2024-05-06 18:27         ` H.J. Lu
2024-05-10 21:46           ` Noah Goldstein
2024-05-11 13:01             ` H.J. Lu
2024-05-07 16:39         ` RFC: ld: Add --text-section-ordering-file (version 4) Nick Clifton
2024-05-10 12:25           ` Alan Modra
2024-05-10 16:00             ` Nick Clifton

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=c234e674-fe64-4b01-b9ad-afd8c65c46e0@redhat.com \
    --to=nickc@redhat.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=siddhesh@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).