This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Adding knowledge of the int_fastN_t types to the compiler, take 2
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: joseph at codesourcery dot com
- Cc: gcc at gcc dot gnu dot org, fortran at gcc dot gnu dot org, fxcoudert at gmail dot com
- Date: Fri, 18 Apr 2008 14:42:40 -0500
- Subject: Re: Adding knowledge of the int_fastN_t types to the compiler, take 2
- Followup-to: <Pine.LNX.4.64.0804181825090.31933@digraph.polyomino.org.uk>
> Also, I think the conclusion was that the compiler should not claim
> any knowledge of these types unless specifically configured for a
> particular target - that is, defaults.h should not contain any default
> definitions.
My strong preference is to just predefine:
__INT8_T__
__INT16_T__
__INT32_T__
__INT64_T__
__UINT8_T__
__UINT16_T__
__UINT32_T__
__UINT64_T__
__INTMAX_T__
__INTPTR_T__
__UINTMAX_T__
__UINTPTR_T__
etc.
Along with all the rest of the predefined bits here:
http://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html
That way we get to avoid playing games with include file defines, which
will just get as ratty as stddef.h over time.
-benjamin
-benjamin