Re: [PATCH] Fix distinction of 32/64bit addresses in MIPS gas

[Thiemo Seufer <ica2_ts at csv dot ica dot uni-stuttgart dot de>]

Eric Christopher wrote:
[snip]
> What do you mean by MIPS ABI? There are:
> 
> o32
> o64
> n32
> eabi
> meabi

64 is missing here.

[snip]
> What we should probably do for linux (since that seems to be what you
> really care about) is to do one of two things:

mips-linux is very different from mips64-linux WRT.

> a) take n32, this will ensure that we can deal with sgi programs
> b) take Sys V with the MIPS extensions this is also sane.

mips-linux supports 32bit CPU's, so o32 is the only one of these
ABI's that is usable.

mips64-linux has currently a o32 ABI, too, because there is no
appropriate toolchain for something else. This is obviously not
what's desireable.

> I'm open to discussion and other ideas, but you need to be _much_ more
> specific about what you mean when discussing mips abis.

o64 is a low performance 64bit ABI which is AFAIK not even
documented.

Implementing the full n32 or 64 ABI as defined by SGI would e.g.
introduce Quickstart, which is rather weird and obsoleted by
libc prelinking.

I don't know if (m)eabi can replace n32 on linux, what are
the differences mtween these ABI's?


Thiemo