From c70088c172c537833884e296449995fa4bcf1a5c Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 08:20:58 +0100 Subject: [PATCH 1/1] start filling in --- isa_conflict_resolution.mdwn | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) 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) -- 2.30.2