(no commit message)

[libreriscv.git] / openpower / sv / int_fp_mv.mdwn

diff --git a/openpower/sv/int_fp_mv.mdwn b/openpower/sv/int_fp_mv.mdwn
index fe022652755f7b6cf46ca8625c8783c765366f44..225fd684b7290baf53560b57a9f805ddce11e2bc 100644 (file)
--- a/openpower/sv/int_fp_mv.mdwn
+++ b/openpower/sv/int_fp_mv.mdwn
@@ -24,8 +24,10 @@ Libre-SOC will be compliant with the
 and with its focus on modern 3D GPU hybrid workloads represents an
 important new potential use-case for OpenPOWER.
 
-The progressive development of the Scalar parts of the Power ISA assumed
-that VSX would be there to complement it. However With VMX/VSX 
+Prior to the formation of the Compliancy Levels first introduced
+in v3.0C and v3.1
+the progressive historic development of the Scalar parts of the Power ISA assumed
+that VSX would always be there to complement it. However With VMX/VSX 
 **not available** in the newly-introduced SFFS Compliancy Level, the
 existing non-VSX conversion/data-movement instructions require load/store
 instructions (slow and expensive) to transfer data between the FPRs and
@@ -105,6 +107,9 @@ Those same semantics are used in some way by all of the following languages (not
 
 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).
 
+This instruction is present in ARM assembler as FJCVTZS
+<https://developer.arm.com/documentation/dui0801/g/hko1477562192868>
+
 ### Other languages
 
 TODO: review and investigate other language semantics
@@ -115,14 +120,14 @@ All of the following instructions use the standard OpenPower conversion to/from
 
 Integer operands and results being in the GPR is the key differentiator between the proposed instructions
 (the entire rationale) compated to existing Scalar Power ISA.
-All existing Power ISA Scalar conversion instructions, all
+In all existing Power ISA Scalar conversion instructions, all
 operands are FPRs, even if the format of the source or destination
 data is actually a scalar integer.
 
 Note that source and destination widths can be overridden by SimpleV
 SVP64, and that SVP64 also has Saturation Modes *in addition*
 to those independently described here. SVP64 Overrides and Saturation
-work on *both* Fixed *and* Floating Point.
+work on *both* Fixed *and* Floating Point operands and results.
  The interactions with SVP64
 are explained in the  [[int_fp_mv/appendix]]