Message135024
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(). |
|
Date |
User |
Action |
Args |
2011-05-03 10:45:53 | sdaoden | set | recipients:
+ sdaoden, rhettinger, amaury.forgeotdarc, mark.dickinson, pitrou, eric.smith, stutzbach, meador.inge, xuanji |
2011-05-03 10:45:53 | sdaoden | set | messageid: <1304419553.5.0.663797354743.issue10044@psf.upfronthosting.co.za> |
2011-05-03 10:45:52 | sdaoden | link | issue10044 messages |
2011-05-03 10:45:52 | sdaoden | create | |
|