From aea4b5119eec4d00ea595b1a4beaadb91514cd7b Mon Sep 17 00:00:00 2001 From: lkcl Date: Sat, 19 Dec 2020 18:24:17 +0000 Subject: [PATCH] --- openpower/sv/svp_rewrite/svp64.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openpower/sv/svp_rewrite/svp64.mdwn b/openpower/sv/svp_rewrite/svp64.mdwn index f631fe6e3..2003722f7 100644 --- a/openpower/sv/svp_rewrite/svp64.mdwn +++ b/openpower/sv/svp_rewrite/svp64.mdwn @@ -439,7 +439,7 @@ CR element*. Greatly simplified pseudocode: CRs[8+i].gt = iregs[RT+i] > 0 ... -If a "cumulated" CR based analysis of results is desired, then a followup instruction must be performed, setting "reduce" mode on the Vector of CRs, using cr ops to do so. This provides far more flexibility in analysing vectors than standard Vector ISAs. Normal Vector ISAs are typically restricted to "were all results nonzero" and "were some results nonzero". The application of mapreduce to Vectorised cr operations allows far more sophisticated analysis. +If a "cumulated" CR based analysis of results is desired (a la VSX CR6) then a followup instruction must be performed, setting "reduce" mode on the Vector of CRs, using cr ops to do so. This provides far more flexibility in analysing vectors than standard Vector ISAs. Normal Vector ISAs are typically restricted to "were all results nonzero" and "were some results nonzero". The application of mapreduce to Vectorised cr operations allows far more sophisticated analysis. (see [[discussion]]. some alternative schemes are described there) -- 2.30.2