public inbox for gnu-gabi@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Alan Modra <amodra@gmail.com>, Fangrui Song <i@maskray.me>
Cc: 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: Wed, 9 Nov 2022 11:09:11 +0000	[thread overview]
Message-ID: <f3505a3a-ba97-db01-b1be-cc2e35440651@redhat.com> (raw)
In-Reply-To: <Y2mPzcZHNEv4LCqT@squeak.grove.modra.org>

Hi Guys,

   OK, I agree that using the section flags is a bad idea.

   Using an extended section types is a nice idea, but I think that
   it will probably not solve the underlying problem of inconsistent
   section stripping - we would still need to persuade the tool
   maintainers to agree on which section types are stripped with each
   given strip option, and when new types are added the options would
   have to be updated.

   For now I think that the KISS principle applies.  The strip tools
   have methods for explicitly specifying which sections should be
   removed, so whilst it might be a bit cumbersome if lots of sections
   have to specified, it can be done.

   Extension suggestion withdrawn.

Cheers
   Nick



      reply	other threads:[~2022-11-09 11:09 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
2022-11-09 11:09       ` Nick Clifton [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=f3505a3a-ba97-db01-b1be-cc2e35440651@redhat.com \
    --to=nickc@redhat.com \
    --cc=amodra@gmail.com \
    --cc=gnu-gabi@sourceware.org \
    --cc=guillermo.e.martinez@oracle.com \
    --cc=i@maskray.me \
    --cc=matz@suse.de \
    /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).