From: Carlos O'Donell <carlos@redhat.com>
To: Jozef Lawrynowicz <jozef.l@mittosystems.com>
Cc: Florian Weimer <fweimer@redhat.com>, gnu-gabi@sourceware.org
Subject: Re: [RFC] SHF_GNU_RETAIN ELF Section Flag
Date: Wed, 16 Sep 2020 08:58:41 -0400 [thread overview]
Message-ID: <95e4fd3d-1486-b700-29b0-8b126b24d0ca@redhat.com> (raw)
In-Reply-To: <20200915165255.fm53szwcabht77ig@jozef-acer-manjaro>
On 9/15/20 12:52 PM, Jozef Lawrynowicz wrote:
> I suppose the most compelling use cases for SHF_GNU_RETAIN are when the
> dependency cannot be expressed with references to ELF sections. You
> can't use SHF_GROUP because there is nothing to group the section with.
GRP_KEEP - Group of sections to always keep. Never discarded if included
in the link.
The benefit is you can give them a logical group name e.g. "cpu_features"
and have more than one of them for accounting/documentation purposes.
You can implement a "KEEP" source markup based on gas' .section directive?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-09-16 12:58 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 [this message]
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
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=95e4fd3d-1486-b700-29b0-8b126b24d0ca@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@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).