Message281332
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. |
|
Date |
User |
Action |
Args |
2016-11-21 08:19:52 | gregory.p.smith | set | recipients:
+ gregory.p.smith, pitrou, larry, benjamin.peterson, ned.deily, sjt, python-dev, koobs, alecsandru.patrascu |
2016-11-21 08:19:52 | gregory.p.smith | set | messageid: <1479716392.64.0.772049305738.issue28032@psf.upfronthosting.co.za> |
2016-11-21 08:19:52 | gregory.p.smith | link | issue28032 messages |
2016-11-21 08:19:52 | gregory.p.smith | create | |
|