At Mon, 12 May 2003 10:56:21 -0400, Daniel Jacobowitz wrote: > On Mon, May 12, 2003 at 11:50:28PM +0900, GOTO Masanori wrote: > > At Mon, 12 May 2003 13:28:47 +0200, > > Guido Guenther wrote: > > > On Mon, May 12, 2003 at 07:51:04PM +0900, GOTO Masanori wrote: > > > > BTW, is mips64 biarch issue similar to sparc64/amd64/s390x? If so, > > > > Arnd and Gerhard works (that merges *-64 archs into one lib64c > > > > package) can be applied to mips64? > > > It's a bit more complicated. We have actually three ABIs o32 (which is > > > what we're currently using), n64 and n32. I didn't get around to play > > > with these things yet though. > > > > Could you tell me what the different is in o32/n32/n64, or teach the > > pointer? I sometimes see such names, but I don't know why three ABIs > > are used. > > o32 supports 32-bit-only processors; n32 is essentially a 32-bit ABI, > but supports and requires 64-bit instructions, has more effecient > calling sequences, and uses the FPU better; n64 is a standard 64-bit > ABI.
Thanks for your explanation. I have question more: - What is the status or direction to use o32/n32/n64? - Will o32 be dropped, or three ABIs are coexistence at the same time? - If 3 ABIs are mixed, what is happened? Regards, -- gotom
