Mark Dickinson added the comment: > I think following patch doesn't introduce undefined behavior.
Agreed. As I recall, the memcpy trick is a fairly standard way around this issue, for compilers that are smart enough to compile away the actual memcpy call. > I don't know wherever the patch can cause performance regression on other > platforms or compilers. Me neither. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25823> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
