From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "H.J. Lu via Binutils" <binutils@sourceware.org>,
Kaylee Blake <klkblake@gmail.com>
Subject: Re: [PATCH 0/6] ELF: Strip section header in ELF objects
Date: Tue, 30 May 2023 11:51:00 -0700 [thread overview]
Message-ID: <CAMe9rOrZk14rX_HEyEHt5zjKGavRN7oukkRZMGECgnkqrbNh3w@mail.gmail.com> (raw)
In-Reply-To: <87cz2hacah.fsf@igel.home>
On Tue, May 30, 2023 at 11:45 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> On Mai 30 2023, H.J. Lu via Binutils wrote:
>
> > Section header isn't mandatory on ELF executable nor shared library.
> > This patch set adds a new linker option, -z nosectionheader, to omit ELF
> > section header, an new objcopy and strip option, --strip-sections, to
> > remove ELF section header.
>
> IMHO --strip-sections is too easily confused with --remove-section. How
> about naming it --strip-section-headers?
>
Good point.
Thanks.
--
H.J.
next prev parent reply other threads:[~2023-05-30 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 17:12 H.J. Lu
2023-05-30 17:12 ` [PATCH 1/6] " H.J. Lu
2023-05-31 1:38 ` Alan Modra
2023-05-31 17:15 ` H.J. Lu
2023-05-31 23:43 ` Alan Modra
2023-05-30 17:12 ` [PATCH 2/6] bfd: Improve nm and objdump without section header H.J. Lu
2023-05-30 17:12 ` [PATCH 3/6] ld: Add a simple test for -z nosectionheader H.J. Lu
2023-05-30 17:12 ` [PATCH 4/6] binutils: Add a --strip-sections test H.J. Lu
2023-05-30 17:12 ` [PATCH 5/6] ld: Add tests for -z nosectionheader and --strip-sections H.J. Lu
2023-05-30 17:12 ` [PATCH 6/6] ld: Add -z nosectionheader test to bootstrap.exp H.J. Lu
2023-05-30 18:45 ` [PATCH 0/6] ELF: Strip section header in ELF objects Andreas Schwab
2023-05-30 18:51 ` H.J. Lu [this message]
2023-06-01 18:24 ` Fangrui Song
-- strict thread matches above, loose matches on Subject: below --
2023-05-30 17:12 H.J. Lu
2020-03-21 0:08 H.J. Lu
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=CAMe9rOrZk14rX_HEyEHt5zjKGavRN7oukkRZMGECgnkqrbNh3w@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=klkblake@gmail.com \
--cc=schwab@linux-m68k.org \
/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).