In several asm routines, a pattern like the following can be found:
__ null_check(obj, oopDesc::klass_offset_in_bytes());
__ load_klass(klass, obj, tmp);
The null-check logically belongs into load_klass(), though. This becomes apparent in Lilliput, where the klass-offset is different, depending on whether or not Lilliput is enabled.
__ null_check(obj, oopDesc::klass_offset_in_bytes());
__ load_klass(klass, obj, tmp);
The null-check logically belongs into load_klass(), though. This becomes apparent in Lilliput, where the klass-offset is different, depending on whether or not Lilliput is enabled.
- relates to
-
JDK-8241613 Suspicious calls to MacroAssembler::null_check(Register, offset)
-
- Resolved
-
