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]

Re: GCC build failed with your patch on 2001-01-09T11:35:00Z.


> Cc: rth@redhat.com, gcc@gcc.gnu.org, gcc-regression@gcc.gnu.org,
>         grahams@redhat.com, jsm28@cam.ac.uk, mhayes@redhat.com,
>         neil@daikokuya.demon.co.uk, osk@hem.passagen.se
> From: Alexandre Oliva <aoliva@redhat.com>
> Organization: GCC Team, Red Hat
> Date: 09 Jan 2001 16:56:06 -0200
> User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands)
> 
> On Jan  9, 2001, Geoff Keating <geoffk@geoffk.org> wrote:
> 
> >> Cc: gcc-regression@gcc.gnu.org, grahams@redhat.com, jsm28@cam.ac.uk,
> >> mhayes@redhat.com, neil@daikokuya.demon.co.uk, osk@hem.passagen.se
> >> From: Alexandre Oliva <aoliva@redhat.com>
> >> Organization: GCC Team, Red Hat
> >> Date: 09 Jan 2001 16:22:01 -0200
> 
> >> I can't promise to fix all problems on all 64-bit targets.  I know
> >> there are a number of 64-bit targets that already work with a 64-bit
> >> HOST_WIDE_INT; I was surprised that ppc wasn't one of them.  I'm
> >> pretty sure the problem must be in the ppc back-end, since there are
> >> so many other 64-bit targets that are working correctly.
> 
> > powerpc-eabi is a 32-bit target.
> 
> Then you must arrange for MAX_LONG_TYPE_SIZE to be #undefined or
> #defined to 32 (as long as LONG_TYPE_SIZE isn't wider than that).
> AFAICT, MAX_LONG_TYPE_SIZE is defined to 64, and that's the reason why
> you get a 64-bit HOST_WIDE_INT.

MAX_LONG_TYPE_SIZE is or will be correct, but I still want a 32-bit
HOST_WIDE_INT.

-- 
- Geoffrey Keating <geoffk@geoffk.org>

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