From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 07:22:05 +0000 (+0100) Subject: start filling in X-Git-Tag: convert-csv-opcode-to-binary~5501 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=2935ef67279dc8ae562d0706f624b5e469eb731e;p=libreriscv.git start filling in --- diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index 3a155712b..85da256d0 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -25,10 +25,11 @@ becomes disastrous for the credibility of the entire RISC-V ecosystem. It was also pointed out that Compliance is an extremely important factor to take into consideration, and that Custom Extensions (as being optional) -effectively fall entirely outside of the Compliance Testing. At this -point in the discussion however it was not yet noted the stark problem -that the *mandatory* RISC-V Specification also faces, by virtue of there -being no transitional way to bring in show-stopping critical alterations. +effectively and quite reasonably fall entirely outside of the scope of +Compliance Testing. At this point in the discussion however it was not +yet noted the stark problem that the *mandatory* RISC-V Specification +also faces, by virtue of there being no transitional way to bring in +show-stopping critical alterations. To put this into perspective, just taking into account hardware costs alone: with production mask charges for 28nm being around USD $1.5m,