From 827c14f4e99050ca08974263f01c24965feaae6f Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Tue, 10 Sep 2019 11:48:23 +0100 Subject: [PATCH] update analysis --- ztrans_proposal.mdwn | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/ztrans_proposal.mdwn b/ztrans_proposal.mdwn index 148f9966a..72a0bad05 100644 --- a/ztrans_proposal.mdwn +++ b/ztrans_proposal.mdwn @@ -196,18 +196,14 @@ compliance with such standards, over-and-above what would otherwise be set by a RISC-V Standards Development Process, including both the software compliance and the knock-on implications that has for hardware. -**The "contra"-requirements are**: - -* The requirements are **not** for the purposes of developing a full custom - proprietary GPU with proprietary firmware. -* A full custom proprietary GPU ASIC Manufacturer *may* benefit from - this proposal however the fact that they typically develop proprietary - software that is not shared with the rest of the community likely to - use this proposal means that they have completely different needs. - -This proposal is for *sharing* of effort in reducing development costs, -and as such needs to be entirely public, transparent, and fully integrated -into public upstream libre-licensed libraries and toolchains. +**Collaboration**: + +The case for collaboration on any Extension is already well-known. +In this particular case, the precedent for inclusion of Transcendentals +in other ISAs, both from Graphics and High-performance Computing, has +these primitives well-established in high-profile software libraries and +compilers in both GPU and HPC Computer Science divisions. Collaboration +and shared public compliance with those standards brooks no argument. *Overall this proposal is categorically and wholly unsuited to relegation of "custom" status*. -- 2.30.2