Linker-plugin-based LTO: give an explanation how to use linker-plugin-lto with full LTO #151933
+52
−13
Conversation
This file contains hidden or 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
rustbot
added
the
S-waiting-on-review
Collaborator
|
r? @fee1-dead rustbot has assigned @fee1-dead. Use |
Contributor
Author
|
r? @nnethercote |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Closes #138910
The existing linker-plugin-based LTO documentation does not describe the correct usage of full LTO. Specifically, when invoking
rustcwith full LTO, the-C ltoflag must be passed in addition to-C linker-plugin-lto.Also, this PR documents the use of full LTO when linking Rust with Fortran. Unfortunately, LLVM
flangdoes not currently support ThinLTO, so full LTO is the only viable option in this case.Toolchain combinations were slightly updated.