From: lkcl <lkcl@web>
Date: Sun, 3 Apr 2022 15:06:16 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: opf_rfc_ls005_v1~2900
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=5fac6dfdc27d371f687bd20b856d89f8056cd5d3;p=libreriscv.git

---

diff --git a/openpower/sv/normal.mdwn b/openpower/sv/normal.mdwn
index c7cebb0f5..afb375d0c 100644
--- 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