From cf83c9f89fc6b60b3d1a0cde058da8a5b2b74c91 Mon Sep 17 00:00:00 2001
From: lkcl <lkcl@web>
Date: Tue, 19 Jan 2021 14:47:22 +0000
Subject: [PATCH]

---
 openpower/sv/remap.mdwn | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/openpower/sv/remap.mdwn b/openpower/sv/remap.mdwn
index 83509c18e..69d5295c5 100644
--- a/openpower/sv/remap.mdwn
+++ b/openpower/sv/remap.mdwn
@@ -172,7 +172,13 @@ It should be clear that a 4x4 by 4x4 Matrix Multiply, being effectively the same
 
 # SUBVL Remap
 
-Remapping even of SUBVL (vec2/3/4) elements is permitted, as if the sub-vectir elements were simply part of the main VL loop.  This is the *complete opposite* of predication which **only** applies to the whole vec2/3/4.
+Remapping even of SUBVL (vec2/3/4) elements is permitted, as if the sub-vectir elements were simply part of the main VL loop.  This is the *complete opposite* of predication which **only** applies to the whole vec2/3/4.  In pseudocode this would be:
+
+      for (i = 0; i < VL; i++)
+        if (predval & 1<<i) # apply to VL not SUBVL
+          for (j = 0; j < SUBVL; j++)
+             id = i*SUBVL + j # not, "id=i".
+             ireg[RT+remap1(id)] ...
 
 The reason for allowing SUBVL Remaps is that some regular patterns using Swizzle which would otherwise require multiple explicit instructions with 12 bit swizzles encoded in them may be efficently encoded with Remap instead.  Not however that Swizzle is *still permitted to be applied*.
 
-- 
2.30.2