From ebf60d1e0ebba205c83ec62ef5a5da536856714d Mon Sep 17 00:00:00 2001 From: lkcl Date: Thu, 7 Jul 2022 18:14:48 +0100 Subject: [PATCH] --- openpower/transcendentals.mdwn | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/openpower/transcendentals.mdwn b/openpower/transcendentals.mdwn index 53d61ced4..23c31cced 100644 --- a/openpower/transcendentals.mdwn +++ b/openpower/transcendentals.mdwn @@ -85,10 +85,7 @@ be excluded. * Ultra-low-power (smartwatches where GPU power budgets are in milliwatts) * Mobile-Embedded (good performance with high efficiency for battery life) * Desktop Computing -* Server / HPC (2) - -(2) Supercomputing is left out of the requirements as it is traditionally -covered by Supercomputer Vectorisation Standards (such as RVV). +* Server / HPC / Supercomputing **The software requirements are**: @@ -99,20 +96,6 @@ covered by Supercomputer Vectorisation Standards (such as RVV). seeking public Certification and Endorsement from the Khronos Group under their Trademarked Certification Programme. -**The "contra"-requirements are**: - - Ultra Low Power Embedded platforms (smart watches) are sufficiently - resource constrained that Vectorisation (of any kind) is likely to be - unnecessary and inappropriate. -* The requirements are **not** for the purposes of developing a full custom - proprietary GPU with proprietary firmware driven by *hardware* centric - optimised design decisions as a priority over collaboration. -* 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 - # Proposed Opcodes vs Khronos OpenCL vs IEEE754-2019 This list shows the (direct) equivalence between proposed opcodes, -- 2.30.2