RFR #2 (M) 8148146: Integrate new internal Unsafe entry points, and basic intrinsic support for VarHandles
John Rose
john.r.rose at oracle.com
Wed Feb 17 03:30:47 UTC 2016
On Feb 15, 2016, at 4:22 AM, Aleksey Shipilev <aleksey.shipilev at oracle.com> wrote:
>
> c) unsafe.cpp gets the basic native method implementations. Most new
> operations are folded to their volatile (the strongest) counterparts,
> hoping that compilers would intrinsify them into more performant versions.
A simpler way to accomplish this would be to give the folded API points non-native method bodies, redirecting to whatever native they are folded to.
This will move most of the folding choices up to Java code. A fair amount of movement in unsafe.cpp will disappear.
The non-native folded methods would still be marked @HSIC and be optimized accordingly.
— John
More information about the jdk9-dev
mailing list