You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: src/summary.adoc
+3-3
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ This means the following state is added:
38
38
* Tags in registers, caches, and memory:
39
39
40
40
** Every register has a one-bit tag, indicating whether the capability in the register is valid to be dereferenced.
41
-
This tag is cleared if the register is written as an integer.
41
+
Among other reasons, this tag is cleared if the register is written as an integer.
42
42
43
43
** The tags are also tracked through the memory subsystem: every aligned CLEN-bits wide region has a non-addressable one-bit tag, which the hardware manages atomically with the data.
44
44
The tag is cleared if the memory region is ever written other than using a capability store from a tagged capability register.
@@ -58,7 +58,7 @@ Changing the bounds used for instruction fetch or the pointer mode can be as eas
58
58
<<MODESW_CAP>> and <<MODESW_INT>> instructions are also added to allow cheap mode switching.
59
59
60
60
Exception codes are added for CHERI-specific exceptions on fetch, jumps, and memory access.
61
-
No other exception paths are added: in particular, capability manipulations do not trap, but may clear the tag on the result capability if the operation is not permitted.
61
+
No other exception paths are added: In particular, capability manipulations do not trap, but may clear the tag on the result capability if the operation is not permitted.
62
62
63
63
=== Added Instructions
64
64
@@ -76,7 +76,7 @@ The added instructions can be split into the following categories:
76
76
77
77
=== Existing Instructions
78
78
79
-
Existing RISC-V instructions are largely unmodified: in {cheri_int_mode_name}, there is binary compatibility.
79
+
Existing RISC-V instructions are largely unmodified: In {cheri_int_mode_name}, there is binary compatibility.
80
80
Instructions that access memory, as well as branches and jumps, are automatically checked against <<ddc>> and <<pcc>>, raising an exception if the checks fail.
81
81
However, <<ddc>> and <<pcc>> are reset to <<infinite-cap>> capabilities, meaning the checks will always pass on systems that have not written to CHERI system registers.
0 commit comments