RFR: 8295486: Inconsistent constant field values observed during compilation [v4]

Vladimir Ivanov vlivanov at openjdk.org
Thu Jan 19 18:46:44 UTC 2023


On Thu, 19 Jan 2023 16:38:14 GMT, Tobias Hartmann <thartmann at openjdk.org> wrote:

>> We hit a "not monotonic" assert because the new type of a load from a stable final field is more narrow than the old type which contradicts the assumption that types should only go from TOP to BOTTOM during CCP:
>> 
>> old: `narrowoop: java/lang/Integer:BotPTR:exact *`
>> new: `narrowoop: java/lang/Integer java.lang.Integer {0x000000062c41e548} ...`
>> 
>> or 
>> 
>> old: `narrowoop: java/lang/Integer java.lang.Integer {0x000000062c41e538} ...`
>> new: `narrowoop: java/lang/Integer java.lang.Integer {0x000000062c41e548} ...`
>> 
>> The problem is that a stable field can be (re-)initialized during compilation and since the value is not cached, contradicting types can be observed. In `LoadNode::Value`, we re-read the field value each time: 
>> 
>> https://github.com/openjdk/jdk/blob/872384707e89d03ede655aad16f360dc94f10152/src/hotspot/share/opto/memnode.cpp#L1994-L1997
>> 
>> https://github.com/openjdk/jdk/blob/872384707e89d03ede655aad16f360dc94f10152/src/hotspot/share/opto/type.cpp#L332-L337
>> 
>> The same problem exists for loads from stable arrays:
>> https://github.com/openjdk/jdk/blob/872384707e89d03ede655aad16f360dc94f10152/src/hotspot/share/opto/memnode.cpp#L1923
>> 
>> Caching the field value is not feasible as it would require a cache per ciInstance for all the fields and per ciArray for all the elements. Alternatively, we could keep track of the lookup and only do it once but that would also be lots of additional complexity for a benign issue.
>> 
>> Instead, I propose to skip verification during CCP when folding loads from stable fields. Non-stable, constant fields are not affected as `null` is a valid value for them and they would already be folded before CCP.
>> 
>> Thanks,
>> Tobias
>
> Tobias Hartmann has updated the pull request incrementally with one additional commit since the last revision:
> 
>   NULL -> nullptr

Thanks for doing the cleanups, Tobias! I like how the patch looks now.

src/hotspot/share/ci/ciArray.cpp line 99:

> 97:   GUARDED_VM_ENTRY(
> 98:     ciConstant value = element_value_impl(elembt, get_arrayOop(), index);
> 99:     return check_constant_value_cache(index, value);

If you check the cache first, you don't need to be in VM when doing that.

(As it is now, it doesn't help static/instance fields, but it can be improved. Something for a follow-up cleanup.)

src/hotspot/share/ci/ciObject.hpp line 65:

> 63:   class ConstantValue {
> 64:     private:
> 65:       const ciObject* _obj;

Since `_constant_values` is instance-specific, there's no need in `_obj` anymore, right?

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

PR: https://git.openjdk.org/jdk/pull/11861


More information about the hotspot-compiler-dev mailing list