Gregory P. Smith added the comment: This is no longer a release blocker as --with-lto is not enabled by default by --enable-optimizations since my commits in September.
Regarding --with-lto itself segfaulting... Fixing compiler+linker toolchains is beyond what CPython itself should do. But the reason the flag remains named "optimizations" is that it is fair for us to include --with-lto or other future build time optimization in known good configurations detected by the autoconf configure.ac in the future if desired. I do not think there is anything more for us to do here. We should explicitly _not_ try to add smarts to --with-lto itself as to whether we believe it will build a broken binary or not. ---------- priority: release blocker -> normal resolution: -> not a bug status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28032> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
