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 sdaoden
Recipients amaury.forgeotdarc, eric.smith, mark.dickinson, meador.inge, pitrou, rhettinger, sdaoden, stutzbach, xuanji
Date 2011-05-03.10:45:52
SpamBayes Score 0.01749694
Marked as misclassified No
Message-id <>
Now me.

> When casting from pointer to integer and back again, the resulting
> pointer must reference the same object as the original pointer,
> otherwise the behavior is undefined. That is, one may not use
> integer arithmetic to avoid the undefined behavior of pointer
> arithmetic as proscribed in C99 6.5.6/8.

Say - isn't that a joke about farts of armchair crouchers.
All it says is that if you dereference garbage you get a crash.
If you're concerned, use volatile, and go shoot the compiler
programmer if she dares to optimize just anything.
And on ARM, isn't the interrupt table at ((void*)(char[])0x0)??
La vie est une rose beside that.
And all i need is atomic_compare_and_swap().
Date User Action Args
2011-05-03 10:45:53sdaodensetrecipients: + sdaoden, rhettinger, amaury.forgeotdarc, mark.dickinson, pitrou, eric.smith, stutzbach, meador.inge, xuanji
2011-05-03 10:45:53sdaodensetmessageid: <>
2011-05-03 10:45:52sdaodenlinkissue10044 messages
2011-05-03 10:45:52sdaodencreate