From: lkcl <lkcl@web>
Date: Thu, 7 Jul 2022 10:59:59 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: opf_rfc_ls005_v1~1303
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=1b451fe5c8402f7dc7ac88b16e6cca1ddd91375a;p=libreriscv.git

---

diff --git a/openpower/transcendentals.mdwn b/openpower/transcendentals.mdwn
index cf6458c51..725167099 100644
--- a/openpower/transcendentals.mdwn
+++ b/openpower/transcendentals.mdwn
@@ -122,15 +122,14 @@ their Khronos OpenCL equivalents, and their IEEE754-2019 equivalents.
 98% of the opcodes in this proposal that are in the IEEE754-2019 standard
 are present in the Khronos Extended Instruction Set.
 
-For RISCV opcode encodings see [[rv_major_opcode_1010011]]
-**TODO** replace with OpenPOWER
+Power opcode encodings see [[power_trans_ops]]
 
 See
 <https://www.khronos.org/registry/spir-v/specs/unified1/OpenCL.ExtendedInstructionSet.100.html>
 and <https://ieeexplore.ieee.org/document/8766229>
 
 * Special FP16 opcodes are *not* being proposed, except by indirect / inherent
-  use of the "fmt" field that is already present in the RISC-V Specification.
+  use of elwidth overrides that is already present in the SVP64 Specification.
 * "Native" opcodes are *not* being proposed: implementors will be expected
   to use the (equivalent) proposed opcode covering the same function.
 * "Fast" opcodes are *not* being proposed, because the Khronos Specification