From: Steve McIntyre <steve.mcintyre@linaro.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Roland McGrath <roland@hack.frob.com>,
libc-alpha@sourceware.org, libc-ports@sourceware.org
Subject: Re: ARM hard-float ABI: add ldconfig flag value
Date: Thu, 09 Aug 2012 13:21:00 -0000 [thread overview]
Message-ID: <20120809132012.GT24537@linaro.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1208091107520.10689@digraph.polyomino.org.uk>
On Thu, Aug 09, 2012 at 11:10:28AM +0000, Joseph S. Myers wrote:
>On Thu, 9 Aug 2012, Steve McIntyre wrote:
>
>> >Could you please point to a public statement from the ARM ABI maintainers
>> >about the reservation of these values for the next ABI revision, and the
>> >semantics being assigned to them?
>>
>> There isn't one *yet*, we're waiting on your review before going
>> ahead. If you're happy with the approach here then we'll make that
>> happen ASAP.
>
>The approach of using ELF header flags and testing them in this way is
>fine; as Roland notes some coding style fixes are needed in the patch
>(e.g. spaces before the open parenthesis when calling a function-like
>macro).
OK, easily fixed. :-)
>I just think there should be an actual statement of the ABI before
>the patch goes in. (Such a statement would include the values, the
>types of ELF files for which they may be used (I guess ET_EXEC and
>EY_DYN but not ET_REL) and the semantics of each value.)
ACK. I've forwarded that onto the ABI folks in ARM and they're working
on it. Actually formally publishing a new version of the ABI spec will
likely take a few weeks to go through the system, but hoping to get
some agreed wording and a commitment to publish out long before then.
Cheers,
--
Steve McIntyre steve.mcintyre@linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
next prev parent reply other threads:[~2012-08-09 13:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120727160941.GA13597@linaro.org>
[not found] ` <20120802165658.GG24537@linaro.org>
2012-08-02 17:28 ` Roland McGrath
2012-08-02 17:49 ` Steve McIntyre
2012-08-02 17:55 ` Roland McGrath
2012-08-02 18:14 ` Steve McIntyre
2012-08-02 18:26 ` Roland McGrath
2012-08-03 16:46 ` Steve McIntyre
2012-08-08 13:41 ` Steve McIntyre
2012-08-08 16:31 ` Roland McGrath
2012-08-08 20:02 ` Joseph S. Myers
2012-08-09 0:34 ` Steve McIntyre
2012-08-09 11:10 ` Joseph S. Myers
2012-08-09 13:21 ` Steve McIntyre [this message]
2012-08-22 15:41 ` Steve McIntyre
2012-08-22 16:13 ` Joseph S. Myers
2012-08-23 15:37 ` Steve McIntyre
2012-08-23 20:40 ` Joseph S. Myers
2012-08-23 22:56 ` Steve McIntyre
2012-08-02 20:50 ` Joseph S. Myers
2012-08-03 17:04 ` Steve McIntyre
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=20120809132012.GT24537@linaro.org \
--to=steve.mcintyre@linaro.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.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).