Build with fat LTO objects by default and strip LTO bytecode from static archives #74
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LTO Bytecode is non portable. Let's build everything with fat lto objects then strip the bytecode after the fact. Note: only clang 18 supports fat lto objects
|
Confirmed working with gnu toolchain, building a static file with LTO and fat lto objects strip will now remove the lto bytecode sections from the archive. We'll have to wait until llvm/clang 18 lands in the repo for it's fat lto objects support. |
In the rare case we have to ship any static files, ensure we build with fat LTO objects so we ship actually usable static files as LTO bytecode is non-portable. Any LTO bytecode will be manually stripped from archive files.
|
Good to go now LLVM/clang 18 is in unstable. |
joebonrichie
changed the title
ermo
approved these changes
May 27, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
LTO Bytecode is non portable. Let's build everything with fat lto objects then strip the bytecode after the fact.
Note: only clang 18 supports fat lto objects