This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients alecsandru.patrascu, benjamin.peterson, gregory.p.smith, koobs, larry, ned.deily, pitrou, python-dev, sjt
Date 2016-11-21.08:19:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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 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.
Date User Action Args
2016-11-21 08:19:52gregory.p.smithsetrecipients: + gregory.p.smith, pitrou, larry, benjamin.peterson, ned.deily, sjt, python-dev, koobs, alecsandru.patrascu
2016-11-21 08:19:52gregory.p.smithsetmessageid: <>
2016-11-21 08:19:52gregory.p.smithlinkissue28032 messages
2016-11-21 08:19:52gregory.p.smithcreate