start filling in

[libreriscv.git] / isa_conflict_resolution.mdwn

diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn
index 64fc5cb0cd63da2e64a100b4dd3123136ba31d3c..3a155712bd67aae0ad17baa683d0a8b133e1cc34 100644 (file)
--- 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
 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)
 
 It was also pointed out that Compliance is an extremely important factor
 to take into consideration, and that Custom Extensions (as being optional)