Mark Dickinson <[email protected]> added the comment:
If we're worrying about undefined behaviour, it looks like recent optimizations
have *introduced* new undefined behaviour in the form of strict aliasing
violations. E.g., from ascii_decode:
unsigned long value = *(const unsigned long *) _p;
(here _p has type const char *). This should really be fixed; compilers are
known to make optimizations based on the assumption that this sort of undefined
behaviour doesn't occur.
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue15144>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
