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 mark.dickinson
Recipients amaury.forgeotdarc, eric.smith, mark.dickinson, pitrou, rhettinger, stutzbach
Date 2010-10-07.22:03:46
SpamBayes Score 2.4322674e-07
Marked as misclassified No
Message-id <>
> For the record, a Py_uintptr_t version works and has the same
> performance. Would you agree to it or is there still some menacing 
> oddity from the i386 days lurking around?

Technically, it's still dodgy:  as the gcc manual notes in:

". That is, one may not use integer arithmetic to avoid the undefined behavior of pointer arithmetic as proscribed in C99 6.5.6/8."

I can't see as much scope for problems with the uintptr_t version.  But just because I can't anticipate the problems, it doesn't mean they don't exist.

It really would be better to avoid the undefined behaviour if at all possible.
Date User Action Args
2010-10-07 22:03:49mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, amaury.forgeotdarc, pitrou, eric.smith, stutzbach
2010-10-07 22:03:48mark.dickinsonsetmessageid: <>
2010-10-07 22:03:46mark.dickinsonlinkissue10044 messages
2010-10-07 22:03:46mark.dickinsoncreate