-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to LLVM 13 #87570
Merged
Merged
Upgrade to LLVM 13 #87570
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
2967036
Update codegen tests for LLVM 13
nikic 621f514
Handle SrcMgr diagnostics
nikic 335f003
Remove codegen/issue-83623-SIMD-PartialEq.rs
nikic 6eaf227
Update wasm data layout
nikic b5cc03b
Update powerpc64 data layout
nikic 154c840
Update coverage LLVM IR test
nikic 7c01564
Use llvm.compiler.used insetad of llvm.used
nikic d20e798
Set LLVM_INCLUDE_TESTS=OFF when building LLVM
nikic 6a454ed
Dispose LLVM context after TargetMachine
nikic 3cfb730
Relax internal/private checks in coverage IR test
nikic f3ae726
Update to LLVM 13
nikic 306259c
Always use llvm.used for coverage symbols
nikic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems pretty poor, if we're resorting to doing this we might as well not include the data layout to the target definition at all.
Out of scope for this PR regardless, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the reason the target data layout exist is that rustc needs the information itself for layout calculation and some other things.
But we don't need all the information -- only the parts parsed into TargetDataLayout. So possibly what we could do is reduce the data layout info in targets to just the necessary information, and then only check that this is consistent with the LLVM data layout (but then use the more precise LLVM data layout for code generation).
In these two cases, the newly added information is stack alignment and non-integral address spaces, both of which we don't care about.