From 4caf4f013467080ac1b168f65203cec75bd81bee Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 08:33:05 +0100 Subject: [PATCH] start filling in --- isa_conflict_resolution.mdwn | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index ada220028..b2b3b2124 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -145,13 +145,13 @@ This was one of the first arguments presented: The RISC-V Foundation considers Custom Extensions to be "out of scope"; that "it's not their problem, therefore there isn't a problem". -The logical errors in this argument were quickly enumerated: namely -that the RISC-V Foundation is not in control of the use-cases, such -that binary-encoding is a hundred percent guaranteed to occur, and -a hundred percent guaranteed to occur in *commodity* hardware where -Debian, Fedora, SUSE and other distros will be hardest hit by the -resultant chaos, and that will just be the more "visible" aspect of -the underlying problem. +The logical errors in this argument were quickly enumerated: namely that +the RISC-V Foundation is not in control of the uses to which RISC-V is +put, such that public global conflicts in binary-encoding are a hundred +percent guaranteed to occur, and a hundred percent guaranteed to occur in +*commodity* hardware where Debian, Fedora, SUSE and other distros will +be hardest hit by the resultant chaos, and that will just be the more +"visible" aspect of the underlying problem. # Do nothing (Compliance too complex, therefore out of scope) -- 2.30.2