I'm trying to iron out some of the strict-aliasing warnings that come
up when building the code under Python 3. (Strict aliasing is a C rule
against using the same pointer as two different types, which, when
followed, gives the optimizer a huge advantage. This didn't come up
under Python 2,
On Sat, Oct 13, 2012 at 10:56 PM, Brian Crowell br...@fluggo.com wrote:
union {
void *ptr;
int val;
} uresult, uvalp = { *valp }, unewval = { newval };
...and just after I send that, it occurs to me that the code could
just be trying to store an int in the space
