This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PR16350 patch ping - gcc doesn't understand big-endian ARM
On Thu, Mar 24, 2005 at 11:37:33AM +0000, Richard Earnshaw wrote:
> > > My primary concern is that a single letter here is just not
> > > discriminating enough. Anything less than two letters is just going to
> > > cause problems in the future. Overloading this onto the CPU name means
> > > we need to take care to avoid potential CPU name extensions that might
> > > add 'b' to the processor name. To avoid problems I really think this
> > > should be either 'eb' (preferred) or 'be'.
> >
> > Big-endian target triples that are currently 'out there' are:
> >
> > armeb-unknown-linux-gnu
> > armv4b-unknown-linux-gnu
> > armv5teb-unknown-linux-gnu
> >
> > The first one is the 'generic' big-endian target triple, the second
> > and third are what config.guess comes up with on a big-endian StrongARM
> > resp. big-endian xscale. Linux 2.4.* reports 'armv5b' instead of
> > 'armv5teb' for the xscale.
>
> Then config.guess should be fixed. The middle one of these is simply
> wrong.
config.guess is just reporting what uname(1) tells it.
[root@ixp12eb ~]# uname -a
Linux ixp12eb.wantstofly.org 2.6.12-rc1 #1 Sun Mar 20 19:24:18 CET 2005 armv4b armv4b armv4b GNU/Linux
So.. config.guess should be mapping anything of the form "arm*b" to
'armeb', then?
And similarly, it ought to map all the "arm*l" archs that are out
there (armv3l, armv4l, armv5tel) to 'arm'? Or 'armel'?
thanks,
Lennert