This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Bugs in MIPS FUNCTION_ARG_REGNO_P ?


On Wed, 2004-03-03 at 11:09, Mark Mitchell wrote:
> Eric Christopher wrote:
> 
> >I was just talking about doing this last night. We could probably
> >obsolete it in 3.4 and remove in mainline.
> >
> Wind River is using o64 and it will be the system ABI in the next 
> release of VxWorks for MIPS.  Their Diab toolchain will be supporting 
> this ABI as well, and that toolchain is used o non-VxWorks platforms.   
> So, o64 support in GCC will be necessary for VxWorks and for 
> compatibility with Diab on other platforms.
> 

How on earth are they going to have another toolchain implement an
undocumented abi?

> We should not remove this ABI.  If we did, doing a VxWorks port would 
> require putting it back.
> 
> (The reason they are using o64 is that the MIPS back end no longer 
> allows "-mabi=32 -mgp64" which was what they were using before.  Their 
> codebase identifies itself as GCC 2.96, and is, I believe, a Red Hat 
> delivery, but I might be wrong about the origin.)

It was. It has some other interesting history, but that's a good
summation :)

I can't believe they actually thought that 64-bit regs with a 32-bit abi
was a good idea. As long as they're implementing something have they
thought about n32 which is documented?

-eric

-- 
Eric Christopher <echristo@redhat.com>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]