From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: gnu-gabi@sourceware.org
Subject: Re: Document existing GNU extensions
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <CAMe9rOrQR4nia=STcX2ixAzwLdQEkk4aPV-TPO5ydmGtb-A4_g@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOoXDMLKw1RLK16dL6CbeLt9ACqRmQT0=OkFWZo-=ghH2g@mail.gmail.com>
On Thu, Mar 3, 2016 at 9:23 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Fri, Feb 19, 2016 at 2:52 PM, Mark Wielaard <mark@klomp.org> wrote:
>> On Fri, Feb 19, 2016 at 02:26:15PM -0800, H.J. Lu wrote:
>>> There are many GNU extensions in GCC, binutils and glibc. Some of
>>> them are
>>>
>>> PT_GNU_EH_FRAME
>>> STT_GNU_IFUNC
>>> PT_GNU_STACK
>>> PT_GNU_RELRO
>>> SHT_GNU_INCREMENTAL_INPUTS
>>> SHT_GNU_ATTRIBUTES
>>> SHT_GNU_HASH
>>> SHT_GNU_LIBLIST
>>> SHT_GNU_verdef
>>> SHT_GNU_verneed
>>> SHT_GNU_versym
>>> STB_GNU_UNIQUE
>>> DT_GNU_PRELINKED
>>> DT_GNU_CONFLICTSZ
>>> DT_GNU_LIBLISTSZ
>>> DT_GNU_HASH
>>> DT_GNU_CONFLICT
>>> DT_GNU_LIBLIST
>>> DT_RELCOUNT
>>> DT_RELACOUNT
>>> .note.ABI-tag
>>> .note.GNU-stack
>>
>> That is a nice list to start with, thanks.
>>
>>> Most of their documentations are with the source codes or spread over
>>> multiple email messages in various mailing list archives. There is no
>>> central place to look them up.
>>
>> Right, that is why we set up this group.
>>
>>> I documented 2 of them:
>>>
>>> PT_GNU_EH_FRAME
>>> STT_GNU_IFUNC
>>>
>>> and put them at
>>>
>>> https://github.com/hjl-tools/linux-abi
>>>
>>> Is there a git repo I can use on sourceware.org?
>>
>> Not yet. But we should get one once we have concensus about how to
>> make sure we document things.
>>
>
> FYI, I updated my Linux-abi spec to correct PT_GNU_EH_FRAME
> and add .eh_frame_hdr section.
>
I updated my Linux-abi spec with .note.gnu.build-id section and
NT_GNU_BUILD_ID:
https://github.com/hjl-tools/linux-abi/wiki/Linux-Extensions-to-gABI
--
H.J.
prev parent reply other threads:[~2016-03-04 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 H.J. Lu
2016-01-01 0:00 ` Mark Wielaard
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` H.J. Lu [this message]
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='CAMe9rOrQR4nia=STcX2ixAzwLdQEkk4aPV-TPO5ydmGtb-A4_g@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gnu-gabi@sourceware.org \
--cc=mark@klomp.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).