From: lkcl Date: Thu, 8 Sep 2022 17:21:45 +0000 (+0100) Subject: (no commit message) X-Git-Tag: opf_rfc_ls005_v1~594 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=8f24df7dca437a4a23b8764850530afc0f448376;p=libreriscv.git --- diff --git a/openpower/sv/rfc/ls001.mdwn b/openpower/sv/rfc/ls001.mdwn index 80f704421..a26420e47 100644 --- a/openpower/sv/rfc/ls001.mdwn +++ b/openpower/sv/rfc/ls001.mdwn @@ -56,9 +56,7 @@ Simple-V has been subdivided into levels akin to the Power ISA Compliancy Levels For now Let us call them "SV Compliancy Levels" to distinguish the two. The reason for the SV Compliancy Levels is the same as for the Power ISA Compliancy Levels (SFFS, SFS): to not overburden implementors with features that they do not need. - *There is no dependence between the two types of Compliancy Levels* - The resources below therefore are not all required for all SV Compliancy Levels but they are all required to be reserved. @@ -112,8 +110,7 @@ even for Multi-Issue microarchitectures. * 75% of one Major Opcode (equivalent to the rest of EXT017) * Five 6-bit operations. -No further opcode space *for Simple-V* is envisaged to be required for at least -the next decade. +No further opcode space *for Simple-V* is envisaged to be required for at least the next decade (including if added on VSX) **SPRs**