From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Thu, 26 Apr 2018 09:41:20 +0000 (+0100)
Subject: start filling in
X-Git-Tag: convert-csv-opcode-to-binary~5486
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=31fe922d783c08d76d0f4c61324a48d9094f7d92;p=libreriscv.git

start filling in
---

diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn
index 3c0d2ab43..b7d187add 100644
--- a/isa_conflict_resolution.mdwn
+++ b/isa_conflict_resolution.mdwn
@@ -380,6 +380,12 @@ So to summarise:
 * The implementation details are clear (and problem-free except for
   vendors who insist on deploying dozens of conflicting Custom Extensions:
   an extreme unlikely outlier).
+* Compliance Testing is straightforward and allows vendors to seek and
+  obtain *multiple* Compliance Certificates with past, present and future
+  variants of the RISC-V Standard (in the exact same processor), in order
+  support legacy customers and provide same customers with a way to avoid
+  "impossible-to-make" decisions that throw out ultra-expensive multi-decade
+  proprietary legacy software at the same as the hardware.
 
 # Conversation Exerpts