fix for 64bit uncleanliness in cp/class.c

Richard Henderson rth@cygnus.com
Sat Jan 22 11:18:00 GMT 2000


On Sat, Jan 22, 2000 at 01:43:01PM -0500, Kaveh R. Ghazi wrote:
> As to your second point about HOST_WIDE_INT being a "long long", I'm
> pretty sure its never supposed to be so.

Incorrect. 

The problem being that we don't have arbitrary size integer support,
only enough for two host integers.  So in supporting cross compiles
from a 32-bit host to a 64-bit target that has a 128-bit integer type,
we need the host to use 64-bit integers as well.

> Hmm, I see xm-alpha-interix.h and alpha/xm-vms.h actually set
> HOST_WIDE_INT to "long long".  This supports your claim, but IMHO, I
> think they might be wrong to do it this way.  Can anyone shed light on
> these config files?

Those are a different type of special case.  A 64-bit machine running
a 32-bit OS.  You get much better optimization when HOST_WIDE_INT is
at least as large as BITS_PER_WORD.


r~


More information about the Gcc-patches mailing list