From dfbfc687d3062793a57bb77719543ab498278a00 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 08:25:15 +0100 Subject: [PATCH] start filling in --- isa_conflict_resolution.mdwn | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index e3a55be3e..f7e06b30b 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -47,9 +47,10 @@ flaws going unpatched, with one of many immediate undesirable consequences being that product in extremely large volume gets discarded into landfill. All and any of the issues that were discussed, and all of those that -were not, can be avoided by providing a forwards and backwards -compatible transition path between the current and future *mandatory* -parts of revisions of the RISC-V ISA Standard. +were not, can be avoided by providing a hardware-level runtime-enabled +forwards and backwards compatible transition path between *all* parts +(mandatory or not) of current and future revisions of the RISC-V ISA +Standard. The rest of the discussion - indicative as it was of the stark mutually exclusive gap being faced by the RISC-V ISA Standard given that it does -- 2.30.2