-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: None
-
Component/s: core-libs
-
None
-
b19
In JDK-8187826 we changed to use a NamedFunction for the UNSAFE field, but it appears the invocation mode and the exception type is wrong. This mismatch appears to be ignored by HotSpot, but a user implementing an experimental JVM ran into some issues.
Use REF_getStatic and expect NoSuchFieldException when setting up NF_UNSAFE
Use REF_getStatic and expect NoSuchFieldException when setting up NF_UNSAFE