From: Alan Modra <amodra@gmail.com>
To: Fangrui Song <i@maskray.me>
Cc: Nick Clifton <nickc@redhat.com>, Michael Matz <matz@suse.de>,
gnu-gabi@sourceware.org,
"Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
Subject: Re: Using section flags to indicate stripable or persistent sections
Date: Tue, 8 Nov 2022 09:37:57 +1030 [thread overview]
Message-ID: <Y2mPzcZHNEv4LCqT@squeak.grove.modra.org> (raw)
In-Reply-To: <20221107185136.5zpzi4gnnzmbqxrm@gmail.com>
On Mon, Nov 07, 2022 at 10:51:36AM -0800, Fangrui Song wrote:
> I feel that whether .ctf is strippable in various strip modes may be a
> related question. (I tend to suggest a more intuitive rule instead of
> doing some magic to ease the adoption of a new section. Let users do
> --keep-section=xxx for new sections.)
I agree. I think new SHF flags should only be added if there is a
really desperate need for them, or when everyone sees them as such an
elegant solution to a big problem that we all say "Why didn't I think
of that before?"
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-11-07 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 11:22 Nick Clifton
2022-11-07 13:33 ` Michael Matz
2022-11-07 18:51 ` Fangrui Song
2022-11-07 23:07 ` Alan Modra [this message]
2022-11-09 11:09 ` 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=Y2mPzcZHNEv4LCqT@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=gnu-gabi@sourceware.org \
--cc=guillermo.e.martinez@oracle.com \
--cc=i@maskray.me \
--cc=matz@suse.de \
--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).