Subject: Re: MACHINE_ARCH on mips
To: Jonathan Stone <>
From: Jason Thorpe <>
List: tech-toolchain
Date: 07/26/1998 13:36:43
On Sun, 26 Jul 1998 12:58:00 -0700 
 Jonathan Stone <jonathan@DSG.Stanford.EDU> wrote:

 > Nope.  There are just as many problems with that, too.
 > Whatever we do we need a name that means ``is this a MIPS cpu of any
 > flavour'', for Makefile tests and CPP tests where we cant get by with
 > wildcarding.  On mips, that means six choices:
 > 		el vs be
 > 		o32, n32, lp64	models

It's just plain STUPID to say that we'll try and do every MIPS ABI
convention in NetBSD.  We should stick with ILP32 "mipsel" and "mipseb"
and maybe the LP64 "mipsel64" and "mipseb64" on those systems where it
makes sense.

Adding "find-grained" checking via strings in the kernel is just silly,
is incorrect (see my previous example), and overly complex.

Jason R. Thorpe                             
NASA Ames Research Center                            Home: +1 408 866 1912
NAS: M/S 258-5                                       Work: +1 650 604 0935
Moffett Field, CA 94035                             Pager: +1 650 940 5942