From: lkcl <lkcl@web>
Date: Sat, 18 Jun 2022 09:27:05 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: opf_rfc_ls005_v1~1730
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=e4265ae6e6b7b150aeb5ee6e268b70753f083f82;p=libreriscv.git

---

diff --git a/openpower/sv/setvl.mdwn b/openpower/sv/setvl.mdwn
index 52e98cee0..c6233de43 100644
--- a/openpower/sv/setvl.mdwn
+++ b/openpower/sv/setvl.mdwn
@@ -168,28 +168,6 @@ Sub-vector elements are not be considered "Vertical". The vec2/3/4
 is to be considered as if the "single element".  Caveats exist for
 [[sv/mv.swizzle]] and [[sv/mv.vec]] when Pack/Unpack is enabled.
 
-**Predicate Masks**
-
-Registers used as Predicate Masks must *never* be altered by *any*
-instruction when Vertical-First is active.  If more than the available
-predicate registers are required (r3, r10, r30, CR Predicate Fields) then
-because Vertical-First is not that different from executing standard
-Scalar instructions,
-a simple branch-conditional test should be used instead of predication,
-exactly as would normally be done if SVP64 was not in use.
-Alternatively the `setvl` instruction may be called again with the `vf`
-flag set. This tells the hardware to re-assess the use of Predicates
-
-These rules allow Hardware implementors to choose to
-free up the connection
-between registers used as predicates and registers used for standard
-purposes: Hazards need not be created.
-
-Note that each of the registers may each be used as predicates,
-or they may be used for standard normal purposes. If mixed for
-both purposes when Vertical-First is active, the results of execution
-is `UNDEFINED`.
-
 # Pseudocode
 
     // instruction fields: