From: programmerjake Date: Thu, 25 Mar 2021 18:56:27 +0000 (+0000) Subject: fix typos X-Git-Tag: DRAFT_SVP64_0_1~1144 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=28064e8d9fae13398b36ec403f67b3a4ef08c65f;p=libreriscv.git fix typos --- diff --git a/openpower/ISA_WG/Board_letter_26mar2021.mdwn b/openpower/ISA_WG/Board_letter_26mar2021.mdwn index c63cb7472..8c30bd138 100644 --- a/openpower/ISA_WG/Board_letter_26mar2021.mdwn +++ b/openpower/ISA_WG/Board_letter_26mar2021.mdwn @@ -6,6 +6,7 @@ edit history: * 25mar2021 first revision +* fix typos to be sent to: @@ -30,7 +31,7 @@ Normally, such huge ISA development efforts would be instigated, organised and f From reading the PowerISA v3.0C sections we have learned and taken on board that a "Sandbox" opcode exists (EXT22) which is intended for "small private extensions" to the OpenPOWER ISA, and the expectation that these extensions not be supported by upstream tool-chains is something we agree wholeheartedly with, -The problem is that our Bitmanipulation Extension alone, needed for Audio/Video and cryptographic workloads, struggles to fit into that space, and we have not yet added Custom 3D opcodes or the IEEE754 Transcendentals (SIN, COS). +The problem is that our Bit-Manipulation Extension alone, needed for Audio/Video and Cryptographic workloads, struggles to fit into that space, and we have not yet added Custom 3D opcodes or the IEEE754 Transcendentals (SIN, COS). http://libre-soc.org/openpower/bitmanip