CMake: Expose Python LTO Control #980
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before, LTO/IPO was default-enabled for the Python bindings. This can sometimes, e.g. on PPC64le with GCC 6.4.0 on Summit, cause problems in complex enough scenarios and fail to link.
We now expose control via the standardized CMake variable
CMAKE_INTERPROCEDURAL_OPTIMIZATION
. This variable populates theINTERPROCEDURAL_OPTIMIZATION
property of targets but only works really reliably with CMake 3.18+. We keep the default logic to use LTO, use thepybind11::lto
target for older CMake but let the user deactivate the Python LTO by setting theCMAKE_INTERPROCEDURAL_OPTIMIZATION
variable to false.Related to: pybind/pybind11#3006