From 8ef04077fdb29bf1368213e9d46ec82b1d25c2f4 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 08:31:17 +0100 Subject: [PATCH] start filling in --- isa_conflict_resolution.mdwn | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index 3623a89c7..ada220028 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -125,9 +125,16 @@ space (48-bit, 64-bit) *greater* than that which the chosen core could cope with (32-bit, 48-bit). Overall, none of the options presented were feasible, and, in addition, -even if they were followed through, still would result in the failure -of the RISC-V ecosystem due to global conflicting ISA binary-encoding -meanings (POWERPC's Altivec / SPE nightmare). +with no clear leadership from the RISC-V Foundation on how to avoid +global world-wide encoding conflict, even if they were followed through, +still would result in the failure of the RISC-V ecosystem due to +irreversible global conflicting ISA binary-encoding meanings (POWERPC's +Altivec / SPE nightmare). + +This in addition to the case where the RISC-V Foundation wishes to +fix a critical show-stopping update to the Standard, post-release, +where billions of dollars have been spent on deploying RISC-V in the +field. # Do nothing (out of scope) -- 2.30.2