RFR: 8312495: assert(0 <= i && i < _len) failed: illegal index after JDK-8287061 on big endian platforms
Richard Reingruber
rrich at openjdk.org
Sat Jul 22 06:13:56 UTC 2023
On Fri, 21 Jul 2023 14:24:35 GMT, Richard Reingruber <rrich at openjdk.org> wrote:
> On big endian platforms `jint` values are stored in the high part of `StackValue` values. Therefore the the `StackValue` cannot be cast directly to `jint`. More details why this has to be like this are given in the JBS issue.
>
> This is a common pattern. See also
>
> https://github.com/openjdk/jdk/blob/8d29329138d44800ee4c0c02dacc01a06097de66/src/hotspot/share/runtime/deoptimization.cpp#L1386-L1387
> https://github.com/openjdk/jdk/blob/8d29329138d44800ee4c0c02dacc01a06097de66/src/hotspot/share/runtime/deoptimization.cpp#L1513-L1514
>
> ### Testing
> Manny iterations of vmTestbase/vm/mlvm/meth/stress/compiler/sequences/Test.java.
>
> JTReg tests: tier1-4 of hotspot and jdk. All of Langtools and jaxp. Renaissance benchmarks as functional tests.
>
> All testing was done with fastdebug and release builds on the main platforms and also on Linux/PPC64le.
Thanks for the feedback!
> > How about introducing something like `jint Value::get_jint()` that can be used in place of this error-prone pattern?
>
> And may be rename current method `get_int()` to `get_intptr()` to match type of return value.
I agree. I thought it should be done in a dedicated RFE. But I can do it in this PR.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/14976#issuecomment-1646500655
More information about the hotspot-compiler-dev
mailing list