From: lkcl Date: Fri, 1 Jan 2021 18:53:01 +0000 (+0000) Subject: (no commit message) X-Git-Tag: convert-csv-opcode-to-binary~661 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=5b9e5a2e1843a1d9d588a755ab73d34841d8254d;p=libreriscv.git --- diff --git a/openpower/sv/overview.mdwn b/openpower/sv/overview.mdwn index d8bf7d194..571d21def 100644 --- a/openpower/sv/overview.mdwn +++ b/openpower/sv/overview.mdwn @@ -594,8 +594,8 @@ post-analysed as an unsigned operation. If however "signed" saturation is requested then the actual arithmetic operation has to be carefully analysed to see what that actually means. -In terms of FP arithmetic, which by definition always has a sign bit do -always takes place as a signed operation anyway, the request to saturate +In terms of FP arithmetic, which by definition has a sign bit (so +always takes place as a signed operation anyway), the request to saturate to signed min/max is pretty clear. However for integer arithmetic such as shift (plain shift, not arithmetic shift), or logical operations such as XOR, which were never designed to have the assumption that its