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

---

diff --git a/openpower/sv/int_fp_mv.mdwn b/openpower/sv/int_fp_mv.mdwn
index 16c7af247..db9222d3b 100644
--- a/openpower/sv/int_fp_mv.mdwn
+++ b/openpower/sv/int_fp_mv.mdwn
@@ -52,7 +52,7 @@ If adding new Integer <-> FP conversion instructions,
 the opportunity may be taken to modernise the instructions and make them
 well-suited for common/important conversion sequences:
 
-* **standard** - used by most languages and CPUs
+* **standard IEEE754** - used by most languages and CPUs
 * **standard OpenPOWER** - saturation with NaN
   converted to minimum valid integer
 * **Java** - saturation with NaN converted to 0
@@ -69,7 +69,7 @@ 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 conversion
+## standard IEEE754 conversion
 
 This conversion is outlined in the IEEE754 specification.  It is used
 by nearly all programming languages and CPUs.  In the case of OpenPOWER,
@@ -105,7 +105,7 @@ Those same semantics are used in some way by all of the following languages (not
   instructions when decorated with
   [the `SaturatedConversion` decorator](https://www.khronos.org/registry/spir-v/specs/unified1/SPIRV.html#_a_id_decoration_a_decoration).
 
-### JavaScript FP -> Integer conversion
+### JavaScript conversion
 
 For the sake of simplicity, the FP -> Integer conversion semantics generalized from those used by JavaScripts's `ToInt32` abstract operation will be referred to as [JavaScript conversion semantics](#fp-to-int-javascript-conversion-semantics).