From: Florian Weimer <fweimer@redhat.com>
To: Jozef Lawrynowicz <jozef.l@mittosystems.com>
Cc: Carlos O'Donell <carlos@redhat.com>, gnu-gabi@sourceware.org
Subject: Re: [RFC] SHF_GNU_RETAIN ELF Section Flag
Date: Fri, 18 Sep 2020 20:11:23 +0200 [thread overview]
Message-ID: <877dsr0xbo.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200918100046.r4c3qepxbccp7poc@jozef-acer-manjaro> (Jozef Lawrynowicz's message of "Fri, 18 Sep 2020 11:00:46 +0100")
* Jozef Lawrynowicz:
> Unless we are trying to be protective of the remaining operating
> system-specific section flag bits, I don't really see any downside to
> going the route of SHF_GNU_RETAIN. It is very simple, the linker
> implementation requires only one additional line of code, and the
> definition precisely describes how the section should be treated.
>
> SHF_GNU_RETAIN
> The link editor should not garbage collect the section if it is
> unused.
I don't have any objections to this wording.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-09-18 18:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 12:06 Jozef Lawrynowicz
2020-09-15 12:09 ` Florian Weimer
2020-09-15 12:31 ` Jozef Lawrynowicz
2020-09-15 12:37 ` Florian Weimer
2020-09-15 12:50 ` Carlos O'Donell
2020-09-15 12:55 ` Florian Weimer
2020-09-15 13:29 ` Jozef Lawrynowicz
2020-09-15 14:11 ` Carlos O'Donell
2020-09-15 16:52 ` Jozef Lawrynowicz
2020-09-16 12:58 ` Carlos O'Donell
2020-09-16 13:11 ` Florian Weimer
2020-09-16 13:46 ` Michael Matz
2020-09-18 12:07 ` Florian Weimer
2020-09-18 12:22 ` Jozef Lawrynowicz
2020-09-18 18:09 ` Florian Weimer
2020-09-16 14:13 ` Jozef Lawrynowicz
2020-09-18 10:00 ` Jozef Lawrynowicz
2020-09-18 18:11 ` Florian Weimer [this message]
2020-09-21 12:42 ` Michael Matz
2020-09-21 18:53 ` Jozef Lawrynowicz
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=877dsr0xbo.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=jozef.l@mittosystems.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).