(no commit message)

diff --git a/openpower/sv/remap.mdwn b/openpower/sv/remap.mdwn
index 485a2704691e22b3d9938e2c24975b037d918b99..45e5f9c44110739ce1b22b1ee9e3a0e87dc1c40d 100644 (file)
--- a/openpower/sv/remap.mdwn
+++ b/openpower/sv/remap.mdwn
@@ -229,12 +229,18 @@ all *already* critically depend on overlapping Reads/Writes: Matrix
 uses overlapping registers as accumulators.  Thus the Register Hazard
 Management needed by Indexed REMAP *has* to be in place anyway.
 
+The cost compared to Matrix and other REMAPs (and Pack/Unpack) is
+clearly that of the additional reading of the GPRs to be used as Indices,
+plus the setup cost associated with creating those same Infices.
+If any Deterministic REMAP can cover the required task, clearly it
+is adviseable to use it instead.
+
 *Programmer's note: some algorithms may require skipping of Indices exceeding
 VL-1, not MAXVL-1. This may be achieved programmatically by performing
-a `sv.cmp *RA,RB` where RA is the same GPRs used in the Indexed REMAP,
+an `sv.cmp *BF,*RA,RB` where RA is the same GPRs used in the Indexed REMAP,
 and RB contains the value of VL returned from `setvl`. The resultant
 CR Fields may then be used as Predicate Masks to exclude those operations
-with an Index exceeding VL-1*
+with an Index exceeding VL-1.*
 
 # REMAP area of SVSTATE