(no commit message)

diff --git a/openpower/sv/int_fp_mv.mdwn b/openpower/sv/int_fp_mv.mdwn
index 034907edeeef407d76c5205a24aaaeeedafba908..8d0c3a05e784eb80ddb64708cc4446ac5314a39f 100644 (file)
--- a/openpower/sv/int_fp_mv.mdwn
+++ b/openpower/sv/int_fp_mv.mdwn
@@ -48,19 +48,19 @@ Therefore, we are proposing adding:
 * FPR <-> GPR combined data-transfer/conversion instructions that do
   Integer <-> FP conversions
 
-If we're adding new Integer <-> FP conversion instructions, we may
-as well take this opportunity to modernise the instructions and make them
-well suited for common/important conversion sequences:
+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 Integer -> FP IEEE754 conversion (used by most languages and CPUs)
-* standard OpenPower FP -> Integer conversion (saturation with NaN
-  converted to minimum valid integer)
-* Java FP -> Integer conversion (saturation with NaN converted to 0)
-* JavaScript FP -> Integer conversion (modular with Inf/NaN converted to 0)
+* **standard** - used by most languages and CPUs
+* **standard OpenPOWER** - saturation with NaN
+  converted to minimum valid integer
+* **Java** - saturation with NaN converted to 0
+* **JavaScript** - modulo wrapping with Inf/NaN converted to 0
 
 The assembly listings in the [[int_fp_mv/appendix]] show how costly
-some of these language-specific conversions are: Javascript is 35
-scalar instructions, including four branches.
+some of these language-specific conversions are: Javascript is 32
+scalar instructions, including seven branch instructions.
 
 ## FP -> Integer conversions