This is the mail archive of the
mailing list for the GCC project.
Re: GCC build failed with your patch on 2001-01-09T11:35:00Z.
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: GCC build failed with your patch on 2001-01-09T11:35:00Z.
- From: Jeffrey A Law <law at redhat dot com>
- Date: Tue, 09 Jan 2001 14:30:42 -0700
- cc: Richard Henderson <rth at redhat dot com>, Alexandre Oliva <aoliva at redhat dot com>, Geoff Keating <geoffk at redhat dot com>, gcc at gcc dot gnu dot org, gcc-regression at gcc dot gnu dot org, grahams at redhat dot com, jsm28 at cam dot ac dot uk, mhayes at redhat dot com, neil at daikokuya dot demon dot co dot uk, osk at hem dot passagen dot se, Mark Mitchell <mark at codesourcery dot com>
- Reply-To: law at redhat dot com
In message <200101092020.PAA25574@mal-ach.watson.ibm.com>you write:
> It's not just slowing down a 32-bit target, it is slowing down a
> 32x64 cross when the developer does not want it.
For proper 32x64 HOST_WIDE_INT must be a 64bit type. Yes, things appear to
mostly work if it isn't, but eventually it's going to break if you stress
the tools enough.
I'm not arguing for or against Alex's patch right now (I'm still reading
the thread), but I wanted to make sure that everyone knows there are
correctness issues this patch is trying to address.