From: "H.J. Lu" <hjl.tools@gmail.com>
To: Cary Coutant <ccoutant@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Binutils <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>,
gnu-gabi@sourceware.org, x86-64-abi@googlegroups.com
Subject: Re: RFC: Linux gABI: Add a GNU_PROPERTY_BY_LINKER property
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <CAMe9rOp7C_HS4cg-GcHH6NhT5oP-BxzE9emc6+Szx_-mAvxONw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqHfqfbu_V1bPgykyN352btS8eZpRm-HAwJDfTf_Fiy-Q@mail.gmail.com>
On Tue, Nov 27, 2018 at 11:25 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Tue, Nov 27, 2018 at 9:56 AM Cary Coutant <ccoutant@gmail.com> wrote:
> >
> > > > > PT_GNU_PROPERTY isn't compatible with existing loaders. This needs
> > > > > to be both forward and backward compatible.
> > > >
> > > > Which loaders? The kernel?
> > >
> > > Kernel, glibc, gdb, .....
> >
> > How is that any different from using PT_NOTE? Existing loaders don't
> > handle that either.
> >
> > If you're claiming that a new PT_ value in the program header table
> > will be rejected by existing loaders, that's a bug. It should be
> > fixed. The whole principle of ELF extensibility relies on that.
>
> Add PT_GNU_PROPERTY to cover .note.gnu.property section?
Like:
1. Add PT_GNU_PROPERTY segment type.
# define PT_GNU_PROPERTY (PT_LOOS + 0x474e553)
which covers .note.gnu.property section.
2. Remove GNU_PROPERTY_X86_UINT32_VALID.
--
H.J.
next prev parent reply other threads:[~2018-11-28 0:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` 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 [this message]
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 ` Szabolcs Nagy
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
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=CAMe9rOp7C_HS4cg-GcHH6NhT5oP-BxzE9emc6+Szx_-mAvxONw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=libc-alpha@sourceware.org \
--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).