This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Devin Jeanpierre, mark.dickinson, skrah, vstinner
Date 2013-05-01.19:22:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
"Relying on things like int64_t or uint64_t is tricky, both in
principle *and* in practice. (...) uint64_t and int64_t may be a
stretch, particularly on ARM-style platforms."

I don't understand. Python is already using 64-bit types, in md5
module for example (MD5_INT64). This module is not compiled on ARM?

"In practice, we've had significant difficulties in the past simply
finding and identifying exact-width types in our autoconf machinery:
whether they're defined in <inttypes.h> or <stdint.h> seems to vary
from platform to platform, as does whether they're defined as
typedef's or preprocessor macros."

I don't understand. AC_TYPE_UINT64_T is supposed to provide the
uint64_t (unsigned integer of 64-bit).

Autotool can also generate the stdint.h header if it is not available.
Date User Action Args
2013-05-01 19:22:00vstinnersetrecipients: + vstinner, mark.dickinson, Devin Jeanpierre, skrah
2013-05-01 19:22:00vstinnerlinkissue17884 messages
2013-05-01 19:22:00vstinnercreate