From 0f26d1ba9110dcd0e82946fc6ba690930a4b88a7 Mon Sep 17 00:00:00 2001 From: lkcl Date: Thu, 13 Jun 2019 06:49:45 +0100 Subject: [PATCH] --- isa_conflict_resolution/isamux_isans.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/isa_conflict_resolution/isamux_isans.mdwn b/isa_conflict_resolution/isamux_isans.mdwn index 205278caf..a3a764de7 100644 --- a/isa_conflict_resolution/isamux_isans.mdwn +++ b/isa_conflict_resolution/isamux_isans.mdwn @@ -115,7 +115,7 @@ By coordinating and managing the allocation of namespace bits (unary or binary) # Why ISAMUX / ISANS has to be WLRL and mandatory trap on illegal writes -The namespaces, set by bits in the CSR, are functionally directly equivalent to c++ nanespaces, even down to the use of braces. +The namespaces, set by bits in the CSR, are functionally directly equivalent to c++ namespaces, even down to the use of braces. WARL, by allowing implementors to choose the value, prevents and prohibits the critical and necessary raising of an exception that would begin the JIT process in the case of ongoing standards evolution. -- 2.30.2