-
Notifications
You must be signed in to change notification settings - Fork 9
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
Make store-local violations non-trapping. #26
Merged
Merged
Conversation
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
davidchisnall
force-pushed
the
no-trapping-store-local
branch
from
January 23, 2024 11:23
17f4fef
to
f607df6
Compare
rmn30
reviewed
Jan 23, 2024
davidchisnall
force-pushed
the
no-trapping-store-local
branch
from
January 23, 2024 11:29
f607df6
to
b320127
Compare
Looks fine. However I was planning to set up a change log in the ISA doc before merging any ISA changes and ideally would keep the doc in sync with sail with each commit. |
rmn30
reviewed
Jan 23, 2024
It's difficult to write defensive code if stores may trap depending on the copied value. Allowing store-local to trap makes it easy to force anything that copies on behalf of a caller able to trap by inserting a local capability into the source that it's copying from. This change is already made in CHERIoT Ibex, the spec is catching up. This also removes the associated exception codes. We may wish to reserve them for a debugging mode for finding places where the tag clearing occurs. Fixes #20.
davidchisnall
force-pushed
the
no-trapping-store-local
branch
from
January 23, 2024 11:57
b320127
to
3e16a32
Compare
rmn30
approved these changes
Jan 23, 2024
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.
It's difficult to write defensive code if stores may trap depending on the copied value. Allowing store-local to trap makes it easy to force anything that copies on behalf of a caller able to trap by inserting a local capability into the source that it's copying from.
This change is already made in CHERIoT Ibex, the spec is catching up.
This also removes the associated exception codes. We may wish to reserve them for a debugging mode for finding places where the tag clearing occurs.
Fixes #20.