From 9c862a6bbc48894482fdc938e0aebceeaffb27d4 Mon Sep 17 00:00:00 2001 From: Tim Hutt Date: Mon, 22 Jan 2024 11:37:37 +0000 Subject: [PATCH] Clarify CJALR operation order Clarify that length violations are checked on the address after it has undergone invalid address conversion. Also fix a typo in the title. Fixes #9 --- src/insns/cjalr_jalr_32bit.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/insns/cjalr_jalr_32bit.adoc b/src/insns/cjalr_jalr_32bit.adoc index 6ab8beb6..ec993fe8 100644 --- a/src/insns/cjalr_jalr_32bit.adoc +++ b/src/insns/cjalr_jalr_32bit.adoc @@ -6,7 +6,7 @@ See <> [#JALR,reftext="JALR"] -==== CJAL, JALR +==== CJALR, JALR Synopsis:: Jump and link register @@ -50,7 +50,7 @@ reported in the CAUSE field of <> or <>: | Tag violation | | ✔ | `cs1` has tag set to 0 | Seal violation | | ✔ | `cs1` is sealed and the immediate is not 0 | Permission violation | | ✔ | `cs1` does not grant <> -| Length violation | ✔ | ✔ | Minimum length instruction is not within the target capability's bounds +| Length violation | ✔ | ✔ | Minimum length instruction is not within the target capability's bounds. This check uses the address after it has undergone xref:section_invalid_addr_conv[xrefstyle=short] but with the original bounds. |============================================================================== include::pcrel_debug_warning.adoc[]