From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: Steve McIntyre <steve.mcintyre@linaro.org>,
<libc-alpha@sourceware.org>, <libc-ports@sourceware.org>
Subject: Re: ARM hard-float ABI: add ldconfig flag value
Date: Thu, 02 Aug 2012 20:50:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1208022047500.28917@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20120802172843.AC5092C0DF@topped-with-meat.com>
On Thu, 2 Aug 2012, Roland McGrath wrote:
> libc-ports@sourceware.org is the right list for discussing ARM.
Only for ports patches; the original posting was a patch to a libc file
(sysdeps/generic/ldconfig.h). It could have done with more background
explanation of what these flag values are and how they are used, and
whether and why they do need to be in a single global place rather than
each architecture having its own definitions in sysdeps.
> OSABI is used in a generic way and should not be used for machine-specific
> purposes. 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).
All those values are for obsolete ABI versions and not defined in AAELF.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-08-02 20:50 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
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 [this message]
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=Pine.LNX.4.64.1208022047500.28917@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.com \
--cc=steve.mcintyre@linaro.org \
/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).