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: law at cygnus dot com,Jeffrey A Law <law at hurl dot cygnus dot com>,meissner at cygnus dot com
- Subject: Re: Bootstrap fail related to HOST_WIDEST_INT
- From: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
- Date: Wed, 24 Feb 1999 23:53:06 +0100
- Cc: egcs-bugs at egcs dot cygnus dot com>
- References: <15632.919860088@hurl.cygnus.com>
Am Wed, 24 Feb 1999 schrieb Jeffrey A Law:
>In message <199902241212.MAA19736@sun52.NIS.cambridge>you write:
> > > Then you need to debug why.
> > >
> > > system.h has all the HOST_WIDEST_INT code, it's only a dozen lines or so.
> > >
> > > Is is possible something has defined HOST_WIDEST_INT before system.h has
> > > been included? That's the only way I immediately see for that code
> > > to go wrong.
> > >
> > > jeff
> >
> > You probably need to ensure HOST_BITS_PER_LONGLONG is defined in the
> > relevant host fragment. At least, this was the problem I had on the ARM.
> >
>Ah. Yea, that could definitely lose. I wonder how many xm files don't
>define HOST_BITS_PER_LONGLONG.
>
>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.
Franz.