From ff0221f6bcbb8a99fb55972c5afc70ed1e81b4ba Mon Sep 17 00:00:00 2001
From: Robert Norton <robert.norton@microsoft.com>
Date: Mon, 14 Jun 2021 21:53:42 +0100
Subject: [PATCH] Fix CHERI Exception numbering to match spec.

It looks like PermitUnsealViolation and PermitSetCIDViolation were accidentally renumbered to fill in the gap left by the retired CCallAcessIDCViolation.
---
 src_Core/ISA/CHERIExceptions.bsvi | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/src_Core/ISA/CHERIExceptions.bsvi b/src_Core/ISA/CHERIExceptions.bsvi
index 5a9b839..b4376ee 100644
--- a/src_Core/ISA/CHERIExceptions.bsvi
+++ b/src_Core/ISA/CHERIExceptions.bsvi
@@ -21,6 +21,7 @@
 `CHERIException(PermitSealViolation,      5'd23)
 `CHERIException(PermitASRViolation,       5'd24)
 `CHERIException(PermitCCallViolation,     5'd25)
-`CHERIException(PermitUnsealViolation,    5'd26)
-`CHERIException(PermitSetCIDViolation,    5'd27)
-// 5'd28 - 5'd31 reserved
+// 5'd26 reserved (obsolete CCallAccessIDCViolation)
+`CHERIException(PermitUnsealViolation,    5'd27)
+`CHERIException(PermitSetCIDViolation,    5'd28)
+// 5'd29 - 5'd31 reserved