From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Mark Wielaard <mark@klomp.org>, Cary Coutant <ccoutant@gmail.com>
Cc: nd <nd@arm.com>, "H.J. Lu" <hjl.tools@gmail.com>,
Florian Weimer <fweimer@redhat.com>,
Binutils <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>,
"gnu-gabi@sourceware.org" <gnu-gabi@sourceware.org>,
x86-64-abi <x86-64-abi@googlegroups.com>
Subject: Re: RFC: Add PT_GNU_PROPERTY to cover .note.gnu.property section
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <de080a05-abe0-3b43-1f69-6b3c80a54308@arm.com> (raw)
In-Reply-To: <20181212104449.GB62340@wildebeest.org>
On 12/12/2018 10:44, Mark Wielaard wrote:
> Also I thought there was still a question whether any or all
> newly proposed property features and flags are actually needed
> as loadable segments. There is a clear overlap with the GNU
> Attributes (which are non-loadable). I would like to see consensus
> first on the new property format/flags and which are and which
> aren't needed as loadable properties at runtime.
i think the list of properties that are needed at
runtime can be decided independently, since the
point of the property mechanism is to be extensible
and useful for future features.
i think it is clear that there are at least some
properties that elf loaders will need to check at
runtime, so we do need such a mechanism. (e.g.
PT_GNU_STACK is an existing example that could have
been implemented as a property).
next prev parent reply other threads:[~2018-12-12 12:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 RFC: Linux gABI: Add a GNU_PROPERTY_BY_LINKER property H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` RFC: Add PT_GNU_PROPERTY to cover .note.gnu.property section H.J. Lu
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` Mark Wielaard
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Szabolcs Nagy [this message]
2018-01-01 0:00 ` 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=de080a05-abe0-3b43-1f69-6b3c80a54308@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=nd@arm.com \
--cc=x86-64-abi@googlegroups.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).