From: lkcl <lkcl@web>
Date: Wed, 25 May 2022 10:03:37 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: opf_rfc_ls005_v1~2108
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=d2e05fa600a565a6a3a18502bd35b539d1f0c87a;p=libreriscv.git

---

diff --git a/openpower/sv/int_fp_mv.mdwn b/openpower/sv/int_fp_mv.mdwn
index 8d0c3a05e..16c7af247 100644
--- a/openpower/sv/int_fp_mv.mdwn
+++ b/openpower/sv/int_fp_mv.mdwn
@@ -69,13 +69,13 @@ semantics for FP to Integer conversion.  This section gives an overview
 of the different variants, listing the languages and hardware that
 implements each variant.
 
-## standard Integer -> FP conversion
+## standard conversion
 
 This conversion is outlined in the IEEE754 specification.  It is used
 by nearly all programming languages and CPUs.  In the case of OpenPOWER,
 the rounding mode is read from FPSCR
 
-### standard OpenPower FP -> Integer conversion
+### standard OpenPower conversion
 
 This conversion, instead of exact IEEE754 Compliance, performs
 "saturation with NaN converted to minimum valid integer". This
@@ -85,7 +85,7 @@ OpenPOWER however has instructions for both:
 * rounding mode read from FPSCR
 * rounding mode always set to truncate
 
-### Java FP -> Integer conversion
+### Java conversion
 
 For the sake of simplicity, the FP -> Integer conversion semantics generalized from those used by Java's semantics (and Rust's `as` operator) will be referred to as
 [Java conversion semantics](#fp-to-int-java-conversion-semantics).