RFR: 8256730: Code that uses Object.checkIndex() range checks doesn't optimize well

Paul Sandoz psandoz at openjdk.java.net
Fri Nov 20 16:39:06 UTC 2020


On Fri, 20 Nov 2020 15:05:35 GMT, Nils Eliasson <neliasso at openjdk.org> wrote:

>>> By transforming (CastII (AddI x y)) into (AddI (CastII x) (CastII y))
>> some CastII can be eliminated which improves address computation code.
>> 
>> Wasn't there a recent bugfix that did the opposite? I think it was in a different context but I will try to find out.
>
>>> By transforming (CastII (AddI x y)) into (AddI (CastII x) (CastII y))
> some CastII can be eliminated which improves address computation code.
> 
>> Wasn't there a recent bugfix that did the opposite? I think it was in a different context but I will try to find out.
> 
> False alarm. It was a completely different problem.

Code generation on x86 is good. If also improves other cases, for example https://github.com/richardstartin/vectorbenchmarks/blob/master/src/main/java/com/openkappa/panama/vectorbenchmarks/BitmapLogicals.java#L69

-------------

PR: https://git.openjdk.java.net/jdk/pull/1342


More information about the hotspot-compiler-dev mailing list