The second principle being violated by the above algorithm is the expectation
that temporary storage is available for a modified predicate: there is no
-such space. SVP64 is founded on the principle that all operations are
+such space, and predicates are read-only to reduce complexity at the
+micro-architectural level.
+SVP64 is founded on the principle that all operations are
"re-entrant" with respect to interrupts and exceptions: SVSTATE must
be saved and restored alongside PC and MSR, but nothing more. It is perfectly
fine to have context-switching back to the operation be somewhat slower,