-
Notifications
You must be signed in to change notification settings - Fork 15.1k
[LLVM]Add read and write inaccessible memory metadata #154141
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
Open
CarolineConcatto
wants to merge
6
commits into
llvm:main
Choose a base branch
from
CarolineConcatto:fpmr_metadata_readwrite
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+285
−17
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
d568c2b
[RFC][Draft] Extend MemoryEffects to Support Target-Specific Memory L…
CarolineConcatto 13c7470
Address review comments about tests and names
CarolineConcatto 1987000
Remove old function header that doesn't exist
CarolineConcatto 2dccfa1
Fix test when target memory locations are combined
CarolineConcatto 4366ac7
Fix codegen for opencl tests
CarolineConcatto d926bf7
[LLVM]Add read and write inaccessible memory metadata
CarolineConcatto 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 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
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
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3102,6 +3102,21 @@ Record::getValueAsListOfDefs(StringRef FieldName) const { | |
return Defs; | ||
} | ||
|
||
llvm::IRMemLocation Record::getLocationTypeAsInt(StringRef FieldName) const { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Repeating my earlier comment from the previous review: Can you move the code you added in Record.cpp to CodeGenIntrinsic.cpp and make it a helper function in that file? Make |
||
const Record *LocRec = getValueAsDef(FieldName); | ||
StringRef Name = LocRec->getName(); | ||
if (Name == "AArch64_FPMR") | ||
return static_cast<IRMemLocation>( | ||
llvm::InaccessibleTargetMemLocation::AARCH64_FPMR); | ||
else if (Name == "AArch64_ZA") | ||
return static_cast<IRMemLocation>( | ||
llvm::InaccessibleTargetMemLocation::AARCH64_ZA); | ||
else if (Name == "InaccessibleMem") | ||
return llvm::IRMemLocation::InaccessibleMem; | ||
else | ||
PrintFatalError(getLoc(), "unknown IRMemLocation: " + Name); | ||
} | ||
|
||
int64_t Record::getValueAsInt(StringRef FieldName) const { | ||
const RecordVal *R = getValue(FieldName); | ||
if (!R || !R->getValue()) | ||
|
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
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
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
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.
I still somewhat think we shouldn't embed target-specific bits in IRMemLocation (or at least, I'm not sure having a enum class is a nice idea, doesn't look extendable to other architectures).
@nikic Would it make sense to extend MemoryEffectsBase with a optional storage to maintain target tags (e.g., a vector of
std::pair<TargetMemID, ModRefInfo>
)? The parser/reader could then leverage something similar to getOrInsertSyncScopeID from LLVMContext (i.e.,getOrInsertTargetMemTag("aarch64.za")
to have the TargetMemID, to work on unsigned rather than strings).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.
Let's keep the discussion on #148650.