Skip to content

Commit

Permalink
CHERI-RISC-V: Minor formatting changes
Browse files Browse the repository at this point in the history
  • Loading branch information
PeterRugg committed Aug 1, 2023
1 parent 1d75700 commit 3319e21
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions chap-cheri-riscv.tex
Original file line number Diff line number Diff line change
Expand Up @@ -288,7 +288,7 @@ \subsection{Capability Register File}
capabilities, along with a tag.

Extending general-purpose integer registers raises the
question of whether and how non-capability-aware instructions should
question of whether and how capability-unaware instructions should
interact with capability values in registers -- a concern not dissimilar to
the behavior of instructions on 64-bit architectures offering legacy 32-bit
support.
Expand Down Expand Up @@ -440,7 +440,7 @@ \subsubsection{CHERI Extension Control}
A new bit in the \menvcfg{} and \senvcfg{} CSRs is used to enable
CHERI for lower privilege levels. When CHERI is disabled, attempting
to execute CHERI-specific instructions will raise an illegal
instruction fault including loads and stores which use a capability
instruction fault, including loads and stores which use a capability
register (excluding the implicit \DDC{} operand for legacy
loads/stores) as the memory operand.

Expand Down Expand Up @@ -747,7 +747,7 @@ \subsection{Floating Point}
integer-relative addresses constrained by \DDC{} in integer encoding mode.

The floating point control
registers (FCSR, FRM, and FFlags) are whitelisted in Table \ref{tab:risc-v-access-system-registers-whitelist}
registers (\texttt{fcsr}, \texttt{frm}, and \texttt{fflags}) are whitelisted in Table \ref{tab:risc-v-access-system-registers-whitelist}
so they can be accessed without needing \cappermASR{}.

\subsection{Exception Handling}
Expand Down

0 comments on commit 3319e21

Please sign in to comment.