(no commit message)

diff --git a/openpower/sv/branches.mdwn b/openpower/sv/branches.mdwn
index c77bd3d26163600d538acd277fb33764aafb8f18..c265b1fb12ed65e57a54f9b27dbb5ab6c92a96d4 100644 (file)
--- a/openpower/sv/branches.mdwn
+++ b/openpower/sv/branches.mdwn
@@ -257,17 +257,6 @@ element computation and testing, and the continuation (or otherwise)
 of a given loop. The potential combinations of interactions is why CTR
 testing options have been added.
 
-If both CTR-test and VLSET Modes are requested, it's important to
-observe the correct order: testing the Condition and
-decrementing of CTR is done *before* truncation of VL. In
-other words, the order is strictly (as can be seen in pseudocode, below):
-
-1. compute the test
-2. (optionally) decrement CTR
-3. (optionally) truncate VL
-4. decide (based on step 1) whether to terminate looping
-   (including not executing step 5)
-5. decide whether to branch.
 
 CTR-test mode and CTi interaction is as follows: note that
 `BO[2]` is still required to be clear for decrements to be
@@ -333,6 +322,29 @@ types of decision-making.
 useful, because it can be used to truncate VL to the first predicated
 (non-masked-out) element.
 
+If both CTR-test and VLSET Modes are requested, it's important to
+observe the correct order. What occurs depends on whether VLi
+is enabled, because VLi affects the length, VL.
+
+If VLi (VL truncate inclusive) is set:
+
+1. compute the test
+2. (optionally) decrement CTR
+3. (optionally) truncate VL
+4. decide (based on step 1) whether to terminate looping
+   (including not executing step 5)
+5. decide whether to branch.
+
+If VLi is clear, then when a test fails that element
+and any following it
+should **not** be considered part of the Vector. Consequently:
+
+1) compute the test.
+2) if the test failed, truncate VL to the *previous*
+   element, and terminate looping. No further steps executed.
+3) (optionally) decrement CTR
+4) decide whether to branch.
+
 *Programming note: One important point is that SVP64 instructions are 64 bit.
 (8 bytes not 4). This needs to be taken into consideration when computing
 branch offsets: the offset is relative to the start of the instruction,