RFR: 8230797: ARM32-softfp: assertion in InterpreterRuntime::resolve_ldc [v2]
Coleen Phillimore
coleenp at openjdk.java.net
Tue Jul 6 23:05:57 UTC 2021
On Tue, 6 Jul 2021 13:17:16 GMT, Christoph Göttschkes <cgo at openjdk.org> wrote:
>> Hi,
>>
>> please review the following change, which was way too long on my chest. It fixes an assertion in the template interpreter for ARM32-softfp.
>>
>> For ARM32-softfp, the template interpreter calls into the runtime to load a double constant using the ldc bytecode. After the interpreter loaded the constants, the assert block does some sanity checks on the cached constants. But if the double constant is the first constant to be loaded, the cache is not yet initialized and the check results in a SIGSEGV.
>>
>> I guarded the usage of `ConstantPool::cp_to_object_index` by another check, which tests if there are any resolved references and if that's the case, the cache has already been initialized and the sanity checks can be performed.
>
> Christoph Göttschkes has updated the pull request incrementally with one additional commit since the last revision:
>
> Adds an additional NULL check for the CP _cache.
src/hotspot/share/interpreter/interpreterRuntime.cpp line 193:
> 191: Bytecode_loadconstant ldc2(m, last_frame.bci());
> 192: int rindex = ldc2.cache_index();
> 193: if (rindex < 0 && m->constants()->resolved_references_or_null() != NULL)
I don't see how the code can be running in the interpreter before the rewriter runs, which is in the link stage.
The cp_to_object_index() should return a negative number for the condy on primitive type case.
-------------
PR: https://git.openjdk.java.net/jdk/pull/4582
More information about the hotspot-runtime-dev
mailing list