|sizeof(int) in 64-bit C compilers firstname.lastname@example.org (1995-12-17)|
|Re: sizeof(int) in 64-bit C compilers email@example.com (Jaap van Ganswijk) (1995-12-18)|
|Re: sizeof(int) in 64-bit C compilers firstname.lastname@example.org (Larry Rau) (1995-12-18)|
|Re: sizeof(int) in 64-bit C compilers email@example.com (1995-12-19)|
|Re: sizeof(int) in 64-bit C compilers firstname.lastname@example.org (1995-12-19)|
|Re: sizeof(int) in 64-bit C compilers email@example.com (Richard L. Kennell) (1995-12-19)|
|Re: sizeof(int) in 64-bit C compilers firstname.lastname@example.org (1995-12-28)|
|[1 later articles]|
|From:||email@example.com (Duane Sand)|
|Date:||17 Dec 1995 00:38:50 -0500|
|Keywords:||C, architecture, question|
A number of machines now support 32-bit and 64-bit addressing equally
well, and some even have suitable C compilers that support both forms
of programs. I would like to know which of these compilers have
defined "int" to be 64-bits in their 64-bit-pointer codegen model, and
which compilers have kept "int" as 32-bits as in their 32-bit-pointer
model. The machines where this question arises include
HP-PA, Sparc, Mips, Alpha, PowerPC.
The Mips/SGI compilers define "int" as 32 bits in 32-bit-pointer code,
and 64 bits in 64-bit-pointer code.
This question is not just about C, since this choice tends to affect
register-level call/return conventions for all languages on that
machine, and whether programs can contain a mix of 32- and
Do any of the 64-bit-pointer versions of Unix support a mix of pointer
sizes, via near and far qualifiers? Or do they all insist on all
pointers being equally long?
Return to the
Search the comp.compilers archives again.