This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: egcs mips patch
- To: law at cygnus dot com, Gavin Romig-Koch <gavin at cygnus dot com>
- Subject: Re: egcs mips patch
- From: Martin Knoblauch <knobi at rocketmail dot com>
- Date: Wed, 9 Sep 1998 00:54:48 -0700 (PDT)
- Cc: Jim Wilson <wilson at cygnus dot com>, egcs-patches at cygnus dot com
- Reply-To: knobi at knobisoft dot de
---Jeffrey A Law <law@cygnus.com> wrote:
>
>
> In message <m0zGUGu-000s8GC@cetus.cygnus.com>you write:
> >
> > For 64 bit mips targets, if -mips1 or -mips2 is set, LONG_MAX is
not
> > correct. Is this OK to push?
> >
> > -gavin...
> >
> >
> > * mips/abi64.h (LONG_MAX_SPEC): Don't set LONG_MAX for
> > mips1 or mips2 either.
> Do -mips1 and -mips2 actually change the size of a long? I guess
> if they do, then the patch is correct.
>
At least for the mips-sgi-irix6.x targets, the following
dependencies are there:
n32: (implies mips3/mips4) long and (void *) are 4 bytes
64: (implies mips3/mips4) long and (void *) are 8 bytes
Pre Irix-6:
o32: (implies mips1/mips2) long and (void *) are 4 bytes
mips-abi: (implies mips1) long and (void *) are 4 bytes
So , for these targets mips1/mips2 definitely restricts the
size of long and (void *) to 4 byte.
Of course, other mips targets may allow 64-bit mips1/mips2
code, or have no dependency on long and (void *).
> I wonder if all this stuff mips abi and -mipsX stuff needs another
> round of cleanups... :-(
Martin
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com