From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 07:20:58 +0000 (+0100) Subject: start filling in X-Git-Tag: convert-csv-opcode-to-binary~5502 X-Git-Url: https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff_plain;h=c70088c172c537833884e296449995fa4bcf1a5c start filling in --- diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index 64fc5cb0c..3a155712b 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -17,9 +17,11 @@ With no transition path there is guaranteed to be tension and conflict within the RISC-V Community over whether revisions should be made: should existing legacy designs be prioritised, mutually-exclusively over future designs (and what happens during the transition period is absolute -chaos). If several overlapping revisions are required that have not -yet transitioned out of use (which could take well over two decades to -occur) the situation becomes disastrous for the credibility of RISC-V. +chaos, with the compiler toolchain, software ecosystem and ultimately +the end-users bearing the full brunt of the impact). If several +overlapping revisions are required that have not yet transitioned out +of use (which could take well over two decades to occur) the situation +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)