Author jared.jennings
Recipients jared.jennings, loewis, theller
Date 2008-10-16.18:29:43
SpamBayes Score 0.00198425
Marked as misclassified No
Message-id <1224181785.66.0.165472132553.issue4130@psf.upfronthosting.co.za>
In-reply-to
Content
According to §7.1.3 of the C99 standard, the name __int128_t is reserved
for implementation-specific use because it starts with an underscore. So
if gcc defines this type and icc does not, that is not a bug in icc; and
if Python uses this type, it will only certainly build using gcc. I
doubt such a dependency was intended, because it is not documented, and
no error was thrown when the autoconf script detected that a compiler
other than GCC was being used.

C99 standard: http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1124.pdf

Exact-width integer types (e.g. int64_t) are documented in §7.18.1.1 of
the above.
History
Date User Action Args
2008-10-16 18:29:45jared.jenningssetrecipients: + jared.jennings, loewis, theller
2008-10-16 18:29:45jared.jenningssetmessageid: <1224181785.66.0.165472132553.issue4130@psf.upfronthosting.co.za>
2008-10-16 18:29:44jared.jenningslinkissue4130 messages
2008-10-16 18:29:43jared.jenningscreate