Skip to content
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.

Sign up for GitHub

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

clarify FoF loads #500

Merged
merged 1 commit into from
Jan 7, 2025
Merged

clarify FoF loads #500

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion src/vector-integration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,9 @@ _no_ CHERI fault will be taken.
This is consistent with other exceptions such as page faults which are only taken
on _active_ elements.

In the case of fault-only-first loads, a trap caused by a CHERI exception will only be taken if it caused by element 0 (and then only if element 0 is active). If another active element causes a CHERI exception then it is treated the same way as other exceptions, the trap is not taken and instead vl is reduced.
In the case of fault-only-first loads, a CHERI bounds violation is only taken if any bytes of element 0 are out of bounds, or if the CHERI bounds are <<section_cap_malformed,malformed>> and there are any _active_ elements.
If another _active_ element causes a CHERI bounds violation then it is treated the same way as other exceptions, the trap is not taken and instead vl is reduced.
All other CHERI fault types, such as tag violations, are taken if there are any _active_ elements.

NOTE: Indexed loads in {cheri_cap_mode_name} check the bounds of every access against
the authority capability in `cs1`. Therefore the approach of having a zero base
Expand Down
Loading