Re: 64-bit mn10300 prologue bug

[Alexandre Oliva <aoliva at cygnus dot com>]

On May 18, 2000, Jeffrey A Law <law@cygnus.com> wrote:

>   In message <orzopnljtf.fsf@saci.lsd.ic.unicamp.br>you write:
>> I picked `long' because it's guaranteed to be at least 32 bits long,
>> and that's exactly the number of bits we need.  Not that more bits
>> would hurt (they wouldn't), but I'd rather not go for a `long long'
>> when a `long' will do.

> The only time a HOST_WIDE_INT will be a long long will be when the
> target needs to support something like TImode and the host only as
> 32bit longs.

Ah!  For some reason, I had always assumed HOST_WIDE_INT was supposed
to be the widest int type available in the build compiler.

Under this new light, I see HOST_WIDE_INT is the obvious solution.
I'll switch to HOST_WIDE_INT (signed, as suggested by rth), and check
it in, since you had pre-approved the patch conditioned to this
change.

-- 
Alexandre Oliva    Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company        aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist    CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me