Re: Document existing GNU extensions

["H.J. Lu" <hjl.tools@gmail.com>]

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.