RFR 8191278: MappedByteBuffer bulk access memory failures are not handled gracefully

[Jamsheed]

Hi Vladimir,

John Rose comments about this issue here.

Adding a mechanism for more precisely mapping the locations of unsafe
memory operations would be more complex (though doable). It would tend
to reduce the optimization level of code which uses unsafe operations.
Therefore, I think the present imprecise design is preferable.

john.rose at Eng <mailto:john.rose at Eng>2001-05-11

https://bugs.openjdk.java.net/browse/JDK-4454115

Best regards,

Jamsheed


On 10/04/19 4:01 AM, Vladimir Kozlov wrote:
> Actually I think the whole code for "// BugId 4454115" is questionable 
> since it replaces any crash (most likely not related to unsafe access) 
> in compiled method which has at least one unsafe access with 
> exception. May be we should use PcDesc to record unsafe instructions 
> and compare with SEGV PC. But it is separate RFE. For this one we need 
> to fix only Unsafe.CopyMemory0() C2 inrinsic.