X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=isa_conflict_resolution.mdwn;h=3a155712bd67aae0ad17baa683d0a8b133e1cc34;hb=c70088c172c537833884e296449995fa4bcf1a5c;hp=64fc5cb0cd63da2e64a100b4dd3123136ba31d3c;hpb=d9e2513bac57717ad4f741f9045184e3c910b54c;p=libreriscv.git

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)