public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Binutils <binutils@sourceware.org>
Cc: hjl.tools@gmail.com, siddhesh@redhat.com
Subject: Re: RFC: ld: Add --text-section-ordering-file (version 4)
Date: Tue, 7 May 2024 17:39:58 +0100	[thread overview]
Message-ID: <fdcca315-ca2f-4818-aa22-608b2b839109@redhat.com> (raw)
In-Reply-To: <Zi7l6irHuTIDwH8i@squeak.grove.modra.org>

[-- Attachment #1: Type: text/plain, Size: 517 bytes --]

Hi Guys,

   So here is an augmented version of Alan's patch.  All that
   it does is to add some documentation and enhance one of the
   tests so that it checks ordering the .data section as well
   as the .text section.

   Any comments ?

   If there is nothing too seriously wrong with it, I would like
   to check the patch in so that we can start testing it in the
   real world.  We can always augment or change it later on, but
   it would be nice to have something that people can play with.

Cheers
   Nick

[-- Attachment #2: section-ordering-file.patch.4 --]
[-- Type: application/x-troff-man, Size: 21073 bytes --]

  parent reply	other threads:[~2024-05-07 16:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 13:01 RFC: ld: Add --text-section-ordering-file (version 2) 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
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         ` Nick Clifton [this message]
2024-05-10 12:25           ` RFC: ld: Add --text-section-ordering-file (version 4) 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=fdcca315-ca2f-4818-aa22-608b2b839109@redhat.com \
    --to=nickc@redhat.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).