From 3f2fcb9cf9886b960fd066a8b342a299aea42088 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 13:01:03 +0100 Subject: [PATCH] clarify --- isa_conflict_resolution.mdwn | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index 25146b669..e0ea58905 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -429,10 +429,11 @@ So to summarise: an extreme unlikely outlier). * Compliance Testing is straightforward and allows vendors to seek and obtain *multiple* Compliance Certificates with past, present and future - variants of the RISC-V Standard (in the exact same processor), in order - support legacy customers and provide same customers with a way to avoid - "impossible-to-make" decisions that throw out ultra-expensive multi-decade - proprietary legacy software at the same as the hardware. + variants of the RISC-V Standard (in the exact same processor, + simultaneously), in order to support legacy customers and provide + same customers with a way to avoid "impossible-to-make" decisions that + throw out ultra-expensive multi-decade proprietary legacy software at + the same as the (legacy) hardware. # Conversation Exerpts -- 2.30.2