This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Target FUNCTION_{PRO,EPI}LOGUE question
- To: jsm28 at cam dot ac dot uk
- Subject: Re: Target FUNCTION_{PRO,EPI}LOGUE question
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Wed, 27 Jun 01 21:11:35 EDT
- Cc: gcc at gcc dot gnu dot org
Why do we have HOST_WIDE_INT rather than using the normal C name "long"
for that concept? Is this just so it can be "long long" when doing 32x64
cross-compiles, because of the limitations of GCC's representations for
target integers, or is there some other reason?
Because it's an abstraction for the "widest integer type" and means precisely
that we don't have to think about the sorts of issues you raise. Note that
there was one (ill-advised) 64-bit ABI which had long as 32 bits and int
as 64 bits.