* Re: Document existing GNU extensions
2016-01-01 0:00 ` H.J. Lu
@ 2016-01-01 0:00 ` H.J. Lu
0 siblings, 0 replies; 5+ messages in thread
From: H.J. Lu @ 2016-01-01 0:00 UTC (permalink / raw)
To: Mark Wielaard; +Cc: gnu-gabi
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Document existing GNU extensions
@ 2016-01-01 0:00 H.J. Lu
2016-01-01 0:00 ` Mark Wielaard
0 siblings, 1 reply; 5+ messages in thread
From: H.J. Lu @ 2016-01-01 0:00 UTC (permalink / raw)
To: gnu-gabi
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
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. 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?
H.J.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Document existing GNU extensions
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
1 sibling, 1 reply; 5+ messages in thread
From: H.J. Lu @ 2016-01-01 0:00 UTC (permalink / raw)
To: Mark Wielaard; +Cc: gnu-gabi
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.
--
H.J.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Document existing GNU extensions
2016-01-01 0:00 ` Mark Wielaard
@ 2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
1 sibling, 0 replies; 5+ messages in thread
From: Michael Matz @ 2016-01-01 0:00 UTC (permalink / raw)
To: Mark Wielaard; +Cc: H.J. Lu, gnu-gabi
Hi,
On Fri, 19 Feb 2016, Mark Wielaard wrote:
> 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)
The global maintainers of at least GCC is a fuzzy definition ...
> to appoint one reviewer/approver who is responsible for making sure
... and I think anyone interested in ABIs should meanwhile be aware of the
existence of this list.
> 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.
Well, as many of the things H.J. listed are effectively part of the
dynamic linker/library/application contract they _are_ part of the ABI,
and better be supportable for basically forever. So documenting existing
behaviour, no matter if intended or accidental, seems worthwhile
independend of anyone actually agreeing that the extension as is is
"fine".
That's of course different with any new proposed extensions.
Ciao,
Michael.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Document existing GNU extensions
2016-01-01 0:00 Document existing GNU extensions 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
0 siblings, 2 replies; 5+ messages in thread
From: Mark Wielaard @ 2016-01-01 0:00 UTC (permalink / raw)
To: H.J. Lu; +Cc: gnu-gabi
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-03-04 18:06 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-01 0:00 Document existing GNU extensions 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 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).