From 1365f26fbdaa04dada847cc6578cb31f72dd8e0e Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Mon, 30 Apr 2018 10:58:51 +0100 Subject: [PATCH] clarify --- isa_conflict_resolution/mvendor_march_warl.mdwn | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/isa_conflict_resolution/mvendor_march_warl.mdwn b/isa_conflict_resolution/mvendor_march_warl.mdwn index 2cb1ea348..f19179818 100644 --- a/isa_conflict_resolution/mvendor_march_warl.mdwn +++ b/isa_conflict_resolution/mvendor_march_warl.mdwn @@ -68,7 +68,8 @@ to not be permitted to receive RISC-V Certification Compliance. How such foreign architectures would switch back to RISC-V when the foreign architecture does not support the concept of mvendorid-marchid is out of -scope and left to implementors. +scope and left to implementors to define and implement equivalent +functionality. ## Implementation @@ -153,3 +154,8 @@ The clear separation which mutually-exclusively redirects encodings based on which mvendorid-marchid tuple is currently active clearly meets that requirement. +# Questions to be resolved + +* Can the declaration (meaning) of read-only be expanded to cover + any number of (non-conflicting) Custom Extensions? What are the + implications of doing so? -- 2.30.2