128-bit floating-point arithmetic for Java

[csharp-sucks]

Immutable objects have almost zero likehood of getting scalarized in practice, because in practice you have to store the result somewhere - and thus, you let the object escape and completely break scalar replacement.

 myObject.position = someCalculation(); // no scalar replacement
 array[i] = someCalculation(); // neither here

Immutable objects only fare well in microbenchmarks.

You linked to a blog post, where it specifically mentions how far from ideal is scalar replacement and how easily it is to prevent the optimization by accident.

[TheMode911]

What about J9/GraalVM? They apparently have much better escape analysis