From: "Peter Collingbourne via gnu-gabi" <gnu-gabi@sourceware.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gnu-gabi@sourceware.org,
"Rafael Ávila de Espíndola" <rafael.espindola@gmail.com>,
"Rui Ueyama" <ruiu@google.com>
Subject: Re: Reserving a section type range for LLVM
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <CAMn1gO4JpvGpQ8txozukzkAM6qqn-UvwrGCmKz-AO3ngqVqZgQ@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqK36XP9q8YKTwEbOnHyTd_EOBj2NxjC3dSQREBHu=SQg@mail.gmail.com>
On Wed, Jun 14, 2017 at 11:12 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Wed, Jun 14, 2017 at 11:03 AM, Peter Collingbourne via gnu-gabi
> <gnu-gabi@sourceware.org> wrote:
>> Any objections to this?
>>
>> Peter
>>
>> On Wed, Jun 7, 2017 at 8:29 PM, Peter Collingbourne <pcc@google.com> wrote:
>>> Hi,
>>>
>>> I am working on a feature in LLVM which will require a special section
>>> type for passing information between the compiler and the linker.
>>>
>>> I see [1] that binutils has defined section types in the range
>>> 0x6fff4700..0x6fff47ff, where presumably the 0x47 ('G') stands for
>>> GNU. In a similar fashion I would like to have the range
>>> 0x6fff4c00..0x6fff4cff reserved for LLVM.
>>>
>>> Thanks,
>>> Peter
>>>
>>> [1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=elfcpp/elfcpp.h;h=cce40d41dedb281c2d8f41135250c2cc39162469;hb=HEAD#l369
>
> There are:
>
> #define SHT_GNU_INCREMENTAL_INPUTS 0x6fff4700 /* incremental build data */
> #define SHT_GNU_ATTRIBUTES 0x6ffffff5 /* Object attributes */
> #define SHT_GNU_HASH 0x6ffffff6 /* GNU style symbol hash table */
> #define SHT_GNU_LIBLIST 0x6ffffff7 /* List of prelink dependencies */
>
> 0x6fff4700 to 0x6fffffff may be used for GNU section types. We can carve
> out 0x6fff4c00..0x6fff4cff for LLVM.
Thanks, sounds good.
Where would be the best place to document this? Should I send a pull
request to https://github.com/hjl-tools/linux-abi ?
Peter
next prev parent reply other threads:[~2017-06-14 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 Peter Collingbourne via gnu-gabi
2017-01-01 0:00 ` Peter Collingbourne via gnu-gabi
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Peter Collingbourne via gnu-gabi [this message]
2017-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=CAMn1gO4JpvGpQ8txozukzkAM6qqn-UvwrGCmKz-AO3ngqVqZgQ@mail.gmail.com \
--to=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=pcc@google.com \
--cc=rafael.espindola@gmail.com \
--cc=ruiu@google.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).