From: Steve McIntyre <steve.mcintyre@linaro.org>
To: Roland McGrath <roland@hack.frob.com>
Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org
Subject: Re: ARM hard-float ABI: add ldconfig flag value
Date: Thu, 02 Aug 2012 17:49:00 -0000 [thread overview]
Message-ID: <20120802174900.GH24537@linaro.org> (raw)
In-Reply-To: <20120802172843.AC5092C0DF@topped-with-meat.com>
Hi Roland,
On Thu, Aug 02, 2012 at 10:28:43AM -0700, Roland McGrath wrote:
>libc-ports@sourceware.org is the right list for discussing ARM.
Ah, OK. I'd seen the mergeback of ports and guessed wrong for the
mailing list. Apologies for that.
>OSABI is used in a generic way and should not be used for machine-specific
>purposes.
Are you sure? Various docs say that values above 64 are specifically
set aside for machine-specific values, hence why I'm looking at using
65 and 66 here.
>An e_flags (EF_*) bit is probably a better choice. There are
>already these bits (among others):
> #define EF_ARM_SOFT_FLOAT 0x200
> #define EF_ARM_VFP_FLOAT 0x400
> #define EF_ARM_MAVERICK_FLOAT 0x800
>But I don't know the history of their use. Off hand EF_ARM_VFP_FLOAT seems
>like it's already what you want, but maybe it has a different meaning (like
>just that it uses VFP, not that the ABI specifies using VFP registers in
>the calling convention).
Exactly, those values are describing needed/used hardware, not ABI.
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-02 17:49 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 [this message]
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
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=20120802174900.GH24537@linaro.org \
--to=steve.mcintyre@linaro.org \
--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).