From: Mark Wielaard <mark@klomp.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gnu-gabi@sourceware.org
Subject: Re: Document existing GNU extensions
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <20160219225240.GF2586@blokker.redhat.com> (raw)
In-Reply-To: <CAMe9rOpv_3mCBGwUGLqVabYJ4NJKrxMfjUouLfrkMAqNTDo5mQ@mail.gmail.com>
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.
I hope we can do it with minimal rules, just discuss any proposals to
document things on this list till there is concensus on the wording.
I propose we invite the global maintainers of each of the GNU toolchain
projects (gcc, gdb, binutils and glibc) to appoint one reviewer/approver
who is responsible for making sure anything we document is actually a
stable GNU gabi extension they are willing to support (and not some
accidental mistake that might seem to work, but was never intented as
public abi). Their job would simply be to say "yes", "no" or "please,
refer to another standard or project documentation as official source"
about any text we come up with that has concensus. That way we make sure
that what we document is actually supported by the GNU toolchain projects
for others to rely on.
Cheers,
Mark
next prev parent reply other threads:[~2016-02-19 22:52 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 [this message]
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
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=20160219225240.GF2586@blokker.redhat.com \
--to=mark@klomp.org \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.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).