This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: ABI / dynamic list now on wiki
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Chris Metcalf <cmetcalf at tilera dot com>
- Cc: <libc-alpha at sourceware dot org>, Richard Henderson <rth at redhat dot com>, Carlos O'Donell <carlos at redhat dot com>, Andreas Schwab <schwab at linux-m68k dot org>, Andreas Krebbel <Andreas dot Krebbel at de dot ibm dot com>, "David S. Miller" <davem at davemloft dot net>, David Holsgrove <david dot holsgrove at xilinx dot com>
- Date: Thu, 23 Jan 2014 16:44:37 +0000
- Subject: Re: ABI / dynamic list now on wiki
- Authentication-results: sourceware.org; auth=none
- References: <Pine dot LNX dot 4 dot 64 dot 1401230114430 dot 16981 at digraph dot polyomino dot org dot uk> <52E14305 dot 2030705 at tilera dot com>
On Thu, 23 Jan 2014, Chris Metcalf wrote:
> On 1/22/2014 8:34 PM, Joseph S. Myers wrote:
> > https://sourceware.org/glibc/wiki/ABIList
>
> There is no actual software stack support for BE tilepro, and as that
> chip architecture is in maintenance mode, we at Tilera are not planning
> to do this work. It is possible in principle but would require both
> kernel and libc work to make it happen. Is it worth calling this out as
> an actual option, given all those caveats?
No, I'd suggest removing the BE entries for tilepro (and probably also
tilegx - in fact I don't see any BE support for that in GCC either).
Having a bits/endian.h that allows for different endiannesses is confusing
when you don't actually have support for those endiannesses.
In general I'd approve of:
* detecting --with-fp / --without-fp by examining what the compiler does
rather than through configure options; and
* detecting subarchitecture variants likewise, with the configure triplet
being less significant; and
* having more sanity checks at configure time that the compiler
configuration is one actually supported for glibc.
--
Joseph S. Myers
joseph@codesourcery.com