From c001b320af59595a5b47ca783b5878390c2c4ba8 Mon Sep 17 00:00:00 2001 From: lkcl Date: Fri, 14 Jun 2019 10:40:35 +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 5bb4dfc56..8d2018854 100644 --- a/isa_conflict_resolution/isamux_isans.mdwn +++ b/isa_conflict_resolution/isamux_isans.mdwn @@ -77,7 +77,7 @@ This to occur immediately and atomically at the point at which the change in ISA The most obvious application of this is for Foreign Archs, which may have their own completely separate PC. Thus, foreign assembly code and RISCV assembly code need not be mixed in the same binary. -Further use-cases may be envisaged however great care needs to be taken to not cause massive complications for JIT emulation. Switching CSR and PC in the RISCV NS needs to be done wisely ane responsibly, i.e. minimised! +Further use-cases may be envisaged however great care needs to be taken to not cause massive complications for JIT emulation, as the RV ISANS is unary encoded (2^31 permutations). Switching CSR and PC in the RISCV unary NS therefore needs to be done wisely and responsibly, i.e. minimised! To be discussed. Context -- 2.30.2