From b4d3ece9cc44c145522034d117471a94aa5a3641 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 08:25:36 +0100 Subject: [PATCH] start filling in --- isa_conflict_resolution.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index f7e06b30b..f1a92a744 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -46,11 +46,11 @@ unpatched tools. This practice is well-known to result in security 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 +**All and any of the issues that were discussed, and all of those that 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. +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