Skip to content

Conversation

@stratakis
Copy link
Contributor

@stratakis stratakis commented Oct 31, 2018

Allow configure --with-lto to apply to all builds, not just profile-opt builds.

This is a backport of #3110

https://bugs.python.org/issue31354

Allow configure --with-lto to apply to all builds, not just profile-opt builds.

Whether this is actually useful or not must be determined by the person
building CPython using their own toolchain.

My own quick test on x86_64 Debian 9 (gcc 6.3, binutils 2.28) seemed
to suggest that it wasn't, but I expect better toolchains can or will exist
at some point.  The point is to allow it at all.
@stratakis
Copy link
Contributor Author

Also #9908 seems to be backported cleanly on top. I'm intending to backport that PR as well if that one is merged.

@vstinner vstinner requested a review from gpshead November 7, 2018 16:00
Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@gpshead: Are you ok to apply this change to 3.6? The final goal is to support LTO compilation using clang. Python 3.6 matters for Red Hat :-)

@gpshead
Copy link
Member

gpshead commented Nov 7, 2018

I'm fine with this in stable releases such as 3.6. My gut feeling is that this will work. It is not going to cause a regression as currently --with-lto doesn't work without PGO so I doubt anyone is using it that way. :)

@vstinner vstinner merged commit f6b9459 into python:3.6 Nov 7, 2018
@vstinner
Copy link
Member

vstinner commented Nov 7, 2018

Ok, let's do that. You can blame me if it breaks the world :-)

@stratakis stratakis deleted the 3.6 branch June 18, 2020 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants