highly suited to High-Performance Computation (HPC), Supercomputing,
and parallel GPU Workloads.
-*Architectural Resource Allocation note: it is prohibited to accept RFCs
+*Architectural Resource Allocation note: at present it is possible to perform
+partial parallel decode of the SVP64 24-bit Encoding at the same time
+as decoding of the Suffix. Multi-Issue Implementations may even
+Decode multiple 32-bit words in parallel and follow up with a second
+cycle of joining Prefix and Suffix "after-the-fact".
+Mixing and overlaying 64-bit Opcode Encodings into the
+{SVP64 24-bit Prefix}{Defined word-instruction} space creates
+a hard dependency that catastrophically damages Multi-Issue Decoding.
+Therefore it has to be 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*
+ that is entirely different from the non-prefixed Defined
+Word.*
Subset implementations in hardware are permitted, as long as certain
rules are followed, allowing for full soft-emulation including future