Added support for retagging subfields of places. #20
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 completes #17, which is v0 of our frontend instrumentation pass.
Retags are added as LLVM intrinsics, which take the following form:
The first parameter is the pointer being retagged. The second is the size of the range for the permission, starting from the base address of the pointer. The third parameter is a flag indicating the type of permission added to the tree (e.g.
Frozen,Reserved), while the fourth is the type of protector applied.Users can control how retags are emitted using
-Zmir-retag-fields=all | none | scalar, which has the same semantics as Miri's-Zmiri-retag-fieldsoption. By default, retagging recurses into fields.