This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Bootstrap fail related to HOST_WIDEST_INT
- To: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
- Subject: Re: Bootstrap fail related to HOST_WIDEST_INT
- From: Jeffrey A Law <law at hurl dot cygnus dot com>
- Date: Thu, 25 Feb 1999 03:03:31 -0700
- cc: meissner at cygnus dot com, egcs-bugs at egcs dot cygnus dot com
- Reply-To: law at cygnus dot com
In message <99022423581000.00834@ns1102.munich.netsurf.de>you write:
> >I bet this is the problem. Franz, if you could take care of the ppc linux
> >port I'll make a pass over the rest of the xm files (boy, what fun that'll
> >be).
>
> The file in question is rs6000/xm-sysv4.h and has HOST_BITS_PER_LONGLONG
> disabled via #if 0. David thought Michael should check why it was disabled.
Michael is unfortunately offline at the moment.
There's only two places in the compiler that would use that value. One is
the newly added to code to determine HOST_WIDEST_INT in system.h, the other
is some code in real.c.
Looking at the code in real.c leads me to believe that defining
HOST_BITS_PER_LONGLONG is safe as long as it's >= HOST_BITS_PER_LONG.
My recommendation would be to remove the #if 0 code. Probably the only
reason it's there was because the compiler never really used the value
provided by HOST_BITS_PER_LONGLONG.
jeff