as the crweird group. Others are to bring the Scalar Power ISA
up-to-date within specific workloads,
such as a JavaScript Rounding instruction
-(which saves 35 instructions including 5 branches) (FIXME: disagrees with int_fp_mv and int_fp_mv/appendix). None of them are strictly
-necessary but performance and power consumption may be (or, is already)
-compromised
+(which saves 32 scalar instructions including seven branch instructions).
+None of them are strictly necessary but performance and power consumption may
+be (or, is already) compromised
in certain workloads and use-cases without them.
Vector-related but still Scalar:
The assembly listings in the [[int_fp_mv/appendix]] show how costly
some of these language-specific conversions are: JavaScript, the
worst case, is 32 scalar instructions including seven branch instructions.
-(FIXME: disagrees with ls006 and sv.mdwn)
# Proposed New Scalar Instructions
### 64-bit float -> 32-bit signed integer
-(FIXME: disagrees with ls006 and sv.mdwn)
-
```
toInt32(double):
stfd 1,-16(1)
**Notes and Observations**:
* These instructions are present in many other ISAs.
-* JavaScript rounding as one instruction saves 35 instructions including
- six branches. (FIXME: disagrees with int_fp_mv and int_fp_mv/appendix)
+* JavaScript rounding as one instruction saves 32 scalar instructions
+ including seven branch instructions.
* Both sets are orthogonal (no difference except being Single/Double).
This allows IBM to follow the pre-existing precedent of allocating
separate Major Opcodes (PO) for Double-precision and Single-precision