STINNER Victor added the comment: Mark Dickinson: "It would also take us even further away from the upstream sources, making it harder to integrate bugfixes from upstream."
We have two main options: * Use -fno-strict-aliasing on clang (solution currently used), maybe restrict the option to dtoa.c * Avoid union to avoid any risk of aliasing issue: option experimented by dim According to Mark, rewriting the code without union is not only more risky but would also be a major shift from upstream. I disagree with it's so risky, there is a risk yes, but we can take our timeto review it and test it on many platforms with the Python extensive test suite. For example, the aliasing issue on clang 4 was catched quicky on our FreeBSD CURRENT buildbot. But the current blocker point is upstream: Mark doesn't want diverge from upstream, so Mark: can you (or someone else?) please contact "Gay (or other maintainers)" to take a decision with him/them? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30124> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
