From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 12:01:03 +0000 (+0100) Subject: clarify X-Git-Tag: convert-csv-opcode-to-binary~5472 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=3f2fcb9cf9886b960fd066a8b342a299aea42088;hp=140255477e1c66d121cfc1e49430a77c58f69475;p=libreriscv.git clarify --- 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