RFR (S): 8218879: Keep track of memory accesses originated from Unsafe
tobias.hartmann at oracle.com
Fri Feb 15 07:28:56 UTC 2019
On 14.02.19 22:18, Vladimir Ivanov wrote:
>> wouldn't it make sense to add this information to MemNode::dump_spec()? Otherwise it's only
>> available via a debugger.
> Yes, good idea. Updated webrev in-place.
> Best regards,
> Vladimir Ivanov
>> Best regards,
>> On 13.02.19 00:30, Vladimir Ivanov wrote:
>>> It may be useful to differentiate memory accesses originated from bytecode and Unsafe.
>>> While JVM performs access checks for field accesses and range checks for array accesses, it's user
>>> responsibility to perform all necessary checks to ensure safety when it comes to Unsafe.
>>> From compiler perspective, it may be useful to distinguish between those when it matters what kind
>>> of checks have been performed.
>>> Testing: hs-precheckin-comp, tier1-5
>>> Best regards,
>>> Vladimir Ivanov
More information about the hotspot-compiler-dev