(no commit message)

diff --git a/openpower/sv/normal.mdwn b/openpower/sv/normal.mdwn
index c7cebb0f5f80ac86fc6adaa59635a580bf8a263c..afb375d0c30e55131c1362bccd5d26780d7d3157 100644 (file)
--- a/openpower/sv/normal.mdwn
+++ b/openpower/sv/normal.mdwn
@@ -95,9 +95,10 @@ the hugely detrimental effect it has on parallel processing, XER.SO is
 overflow bit is therefore simply set to zero if saturation did not occur,
 and to one if it did.
 
-Note also that saturate on operations that produce a carry output are
-prohibited due to the conflicting use of the CR.so bit for storing if
-saturation occurred.
+Note also that saturate on operations that  set OE=1 are
+`UNDEFINED` due to the conflicting use of the CR.so bit for storing if
+saturation occurred. Integer Operations that produce a Carry-Out (CA, CA32):
+these two bits will also be `UNDEFINED` if saturation is requested.
 
 Post-analysis of the Vector of CRs to find out if any given element hit
 saturation may be done using a mapreduced CR op (cror), or by using the