This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: ARM hard-float ABI: add ldconfig flag value
- From: Steve McIntyre <steve dot mcintyre at linaro dot org>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: libc-alpha at sourceware dot org, libc-ports at sourceware dot org
- Date: Thu, 2 Aug 2012 18:49:01 +0100
- Subject: Re: ARM hard-float ABI: add ldconfig flag value
- References: <20120727160941.GA13597@linaro.org> <20120802165658.GG24537@linaro.org> <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