From 07c8153ba493362112cd4bca5c37f24fa63b2355 Mon Sep 17 00:00:00 2001 From: lkcl Date: Wed, 29 Mar 2023 22:33:31 +0100 Subject: [PATCH] --- openpower/sv/rfc/ls010.mdwn | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/openpower/sv/rfc/ls010.mdwn b/openpower/sv/rfc/ls010.mdwn index 6db9dcf5b..c93fb26be 100644 --- a/openpower/sv/rfc/ls010.mdwn +++ b/openpower/sv/rfc/ls010.mdwn @@ -41,18 +41,6 @@ the following instruction, but does **not** change the actual Decoding of that following instruction. **All prefixed instructions retain their non-prefixed encoding and definition**. -*Architectural Resource Allocation note: it is prohibited to accept RFCs -which fundamentally violate this hard requirement. Under no circumstances -must the Suffix space have an alternate instruction encoding allocated -within SVP64 that is entirely different from the non-prefixed Defined -Word. Hardware Implementors critically rely on this inviolate guarantee -to implement High-Performance Multi-Issue micro-architectures that can -sustain 100% throughput* - -| 0:5 | 6:31 | 32:63 | -|--------|--------------|--------------| -| EXT09 | v3.1 Prefix | v3.0/1 Suffix | - Two apparent exceptions to the above hard rule exist: SV Branch-Conditional operations and LD/ST-update "Post-Increment" Mode. Post-Increment was considered sufficiently high priority (significantly reducing hot-loop @@ -62,6 +50,14 @@ Branch-Conditional behaviour into a much more advanced variant that is highly suited to High-Performance Computation (HPC), Supercomputing, and parallel GPU Workloads. +*Architectural Resource Allocation note: it is prohibited to accept RFCs +which fundamentally violate this hard requirement. Under no circumstances +must the Suffix space have an alternate instruction encoding allocated +within SVP64 that is entirely different from the non-prefixed Defined +Word. Hardware Implementors critically rely on this inviolate guarantee +to implement High-Performance Multi-Issue micro-architectures that can +sustain 100% throughput* + Subset implementations in hardware are permitted, as long as certain rules are followed, allowing for full soft-emulation including future revisions. Compliancy Subsets exist to ensure minimum levels of binary -- 2.30.2