From bddbe0447b6a541a49e873efeedf1672d5045337 Mon Sep 17 00:00:00 2001 From: Andres Amaya Garcia Date: Fri, 7 Feb 2025 14:07:00 +0000 Subject: [PATCH] Write note about traps for capability stores (#528) Add a note indicating that capability stores may trap in future extensions when the authorizing capability does not grant capability write permissions. Also remove outdated TODO. Fixes https://github.com/riscv/riscv-cheri/issues/476 --- src/riscv-integration.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/riscv-integration.adoc b/src/riscv-integration.adoc index f2fcfe02..2f260b31 100644 --- a/src/riscv-integration.adoc +++ b/src/riscv-integration.adoc @@ -224,8 +224,9 @@ capability written to memory is cleared if the authorizing capability does not grant permission to write capabilities (i.e. both <> and <> must be set in AP). -WARNING: #TODO: these cases may cause exceptions in the future - we need a way -for software to discover and/or control the behavior# +NOTE: Future extensions to {cheri_base_ext_name} may add mechanisms that cause +stores to raise exceptions when the authorizing capability does not grant both +<> and <>. [#section_existing_riscv_insns] === Existing RISC-V Instructions