LLVM 16: Switch to using MemoryEffects #103977
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.
This adapts the compiler to the changes required by llvm/llvm-project@304f1d5.
AFAICT,
WriteOnly
isn't used by the compiler, allReadNone
uses were migrated and the remaining use ofReadOnly
is only for function parameters.To simplify the FFI, this PR uses an enum to represent
MemoryEffects
across the FFI boundary, which then gets mapped to the matching static factory method when constructing the attribute.Fixes #103961.
@rustbot label +llvm-main
r? @nikic