Steffen Daode Nurpmeso <sdao...@googlemail.com> added the comment: Now me.
(http://gcc.gnu.org/onlinedocs/gcc/Arrays-and-pointers-implementation.html#Arrays-and-pointers-implementation) > 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(). ---------- nosy: +sdaoden _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10044> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
