(no commit message)

diff --git a/openpower/sv/cr_ops.mdwn b/openpower/sv/cr_ops.mdwn
index 424a90885cee873a3c910a0a986c3861943a9a57..5eb5e15dc0947c5442f6d7f20d58928dcb59ed62 100644 (file)
--- a/openpower/sv/cr_ops.mdwn
+++ b/openpower/sv/cr_ops.mdwn
@@ -67,9 +67,9 @@ the main result.
 
 # Format
 
-SVP64 RM `MODE` (includes `ELWIDTH` bits) for CR-based operations:
+SVP64 RM `MODE` (includes `ELWIDTH_SRC` bits) for CR-based operations:
 
-| 4 | 5 | 19-20 |  21 | 22   23 |  description     |
+| 6 | 7 | 19-20 |  21 | 22   23 |  description     |
 | - | - | ----- | --- |---------|----------------- |
 |sz |SNZ| 0 RG  |   0 | dz  /   | normal mode                      |
 |sz |SNZ| 0 RG  |   1 | 0   /   | scalar reduce mode (mapreduce), SUBVL=1 |
@@ -187,14 +187,23 @@ elements thereafter:
 
 # Unusual and quirky CR operations
 
-# cmp and other compare ops
+## cmp and other compare ops
 
 `cmp` and `cmpi` etc take GPRs as sources and create a CR Field as a result.
 
     cmpli BF,L,RA,UI
     cmpeqb BF,RA,RB
 
-With `ELWIDTH_SRC` applying to the source operands this is perfectly fine.
-As an aside it explains why `ELWIDTH` was picked to be used for alternative
-purposes (`SNZ`) rather than `ELWIDTH_SRC`.
+With `ELWIDTH` applying to the source operands this is perfectly fine.
+
+## crweird operations
+
+There are 4 weird CR-GPR operations and one reasonable one in
+the [[cr_int_predication]] set:
+
+* crrweird
+*      mtcrweird
+*      crweirder
+*      crweird
+* mcrfm - reasonably normal and referring to CR Fields for src and dest.