From fbf55d62c21f318234388b754d05241065c099d9 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Mon, 30 Apr 2018 07:58:56 +0100 Subject: [PATCH] reword redraft mvendorid-marchid idea --- isa_conflict_resolution/mvendor_march_warl.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/isa_conflict_resolution/mvendor_march_warl.mdwn b/isa_conflict_resolution/mvendor_march_warl.mdwn index f48c7f0bc..32f2a539b 100644 --- a/isa_conflict_resolution/mvendor_march_warl.mdwn +++ b/isa_conflict_resolution/mvendor_march_warl.mdwn @@ -43,7 +43,7 @@ against *different variants* of past, present and future RISC-V Standards. *This is clearly a desirable characteristic* It's been noted that there may be certain legitimate cases where -an mvendorid-marchid should *specifically* not be tested for RISC-V +a mvendorid-marchid should *specifically* not be tested for RISC-V Certification Compliance: native support for foreign architectures (not related to the JIT Extension: *actual* full entire non-RISC-V foreign instruction encoding). Exactly how this would work (vis-a-vis Compliance) -- 2.30.2