This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Builtin types, <limits.h>, <stdint.h> etc.


Geoff Keating <geoffk@cygnus.com> writes:

|> "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de> writes:
|> 
|> > > There are enough options in GCC to vary the ABI, or to adjust the
|> > > sizes of standard types (e.g. -mint64, -mlong64, -mlong32 on mips;
|> > > -mint32, -mint16 on pdp11) that presuming that a single consistent
|> > > ABI for each platform can be agreed with the vendors seems unwise.
|> ...
|> > For hosted environments, it seems reasonable to expect a single
|> > consistent ABI. Delegating ABI decisions to the compiler user would be
|> > unwise; she normally couldn't care less.
|> 
|> As an example, on AIX/ppc the size of 'long' and pointers can be 32
|> bits or 64 bits, controlled by a compiler switch, and the header files
|> and libraries adjust themselves.
|> 
|> The significance of this is that intptr_t needs to change depending on
|> the setting of this flag.

Strictly speeking, it doesn't, since intptr_t does not need to be exact,
i.e., it can be bigger than necessary.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]