(no commit message)

diff --git a/openpower/transcendentals.mdwn b/openpower/transcendentals.mdwn
index 53d61ced4ba0ef9a38d3b7022af5322b0512e538..23c31ccedece6310f09cd7003f68b88d6c8576f9 100644 (file)
--- 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<a name="khronos_equiv"></a>
 
 This list shows the (direct) equivalence between proposed opcodes,