document that older LLVM versions come with increased risk#2793
Merged
tshepang merged 1 commit intorust-lang:mainfrom Mar 9, 2026
Merged
document that older LLVM versions come with increased risk#2793tshepang merged 1 commit intorust-lang:mainfrom
tshepang merged 1 commit intorust-lang:mainfrom
Conversation
Collaborator
|
Thanks for the PR. If you have write access, feel free to merge this PR if it does not need reviews. You can request a review using |
rustbot
added
the
S-waiting-on-review
Member
Author
|
r? rustc-dev-guide |
nikic
approved these changes
Mar 9, 2026
rustbot
removed
the
S-waiting-on-review
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
I think we should document somewhere that while rustc does build with older versions of LLVM, this comes with an increased risk of soundness bugs since we generally consider miscompilation issues fixed once they are resolved for the latest LLVM. I don't know what the right place for such a statement is -- where do we even document our LLVM support policy? The dev-guide is mostly internal-facing so it doesn't feel like the right place, but it's the best I found so far.
Cc @nikic