Bug ID: JDK-8080588 VarHandles development

JDK-8080588 : VarHandles development

Type: New Feature
Component: core-libs
Sub-Component: java.lang.invoke
Affected Version: 9

Priority: P3
Status: Resolved
Resolution: Fixed
Fix Versions: 9

Submitted: 2015-05-18
Updated: 2016-09-02
Resolved: 2016-09-02

Related Reports

Blocks :	JDK-8153870 - Result-boxed and result-less VarHandles are significantly penalized
Blocks :	JDK-8046183 - JEP 193: Variable Handles
Relates :	JDK-8042997 - Make intrinsic some or all check index/range methods
Relates :	JDK-8135248 - Add utility methods to check indexes and ranges
Relates :	JDK-8141633 - Implement VarHandles/Unsafe intrinsics on AArch64
Relates :	JDK-8141634 - Implement VarHandles/Unsafe intrinsics on SPARC
Relates :	JDK-8131750 - VarHandles JVMS changes
Relates :	JDK-6509032 - (bf) Monomorphic implementations for Direct and Heap versions of X-Buffer
Relates :	JDK-6476827 - (bf spec) Buffer classes need to state memory consistency properties
Relates :	JDK-8008240 - (bf) Atomics for ByteBuffers
Relates :	JDK-8131749 - VarHandles JLS changes
Relates :	JDK-8154447 - Exempt classes under java.util.concurrent from MH.Lookup restrictions

Sub Tasks

JDK-8080590 :	VarHandles for instance fields - Resolved
JDK-8080591 :	VarHandles for static fields - Resolved
JDK-8080592 :	VarHandles for arrays - Resolved
JDK-8080594 :	VarHandles for ByteBuffers - Resolved
JDK-8080595 :	VarHandles for array views - Resolved
JDK-8080596 :	VarHandles API specification - Resolved
JDK-8080597 :	VarHandles unit tests - Resolved
JDK-8080599 :	VarHandles jcstress tests - Resolved
JDK-8080685 :	Unsafe.getAcquire* and VarHandles.getAcquire - Resolved
JDK-8130756 :	MethodType[] VarHandle.types wastes memory - Resolved
JDK-8130758 :	Replace obj.getClass with Objects.requireNonNull - Resolved
JDK-8130920 :	C1 trouble in VarHandle.get tests - Resolved
JDK-8130923 :	C1 trouble in VarHandle.getObject tests - Resolved
JDK-8132229 :	Unsafe.setRelease/putOrdered* for all types - Resolved
JDK-8132327 :	VarHandle access methods should be marked with @HotspotIntrinsicCandidate - Resolved
JDK-8132332 :	Unsafe intrinsics overhaul for VarHandle.{getAcquire\|setRelease} - Resolved
JDK-8132471 :	Introduce VH.{get\|set}Relaxed, and rewire VH.{get\|set} to use the default field access rules - Resolved
JDK-8132472 :	VH.{set\|get}{Acquire\|Release} for raw memory - Resolved
JDK-8133348 :	Reference.reachabilityFence - Resolved
JDK-8133451 :	Add weak CAS, and acquire/release forms of CAS - Closed
JDK-8133568 :	C1 support for Unsafe.{getAcquire\|setRelease} - Closed
JDK-8134293 :	VH.(get\|set)Opaque implementations - Resolved
JDK-8135081 :	Better C1 handling for VarHandles.(get\|set)Opaque - Closed
JDK-8136401 :	Proper implementation for VarHandle.compareAndExchange{Volatile, Acquire, Release} - Closed
JDK-8136761 :	Intrinsics for VarHandle.compareAndExchange{Volatile, Acquire, Release} - Resolved
JDK-8141635 :	Implement VarHandles/Unsafe intrinsics on POWER - Resolved
JDK-8148146 :	Integrate new internal Unsafe entry points, and basic intrinsic support for VarHandles - Resolved
JDK-8149469 :	ByteBuffer API and implementation enhancements for VarHandles - Resolved
JDK-8149644 :	Integrate VarHandles - Resolved
JDK-8151198 :	VarHandle factory-specific exceptions - Closed
JDK-8151705 :	VarHandle.AccessMode enum names should conform to code style - Resolved
JDK-8151706 :	Update VarHandle implementation to use @Stable arrays - Closed
JDK-8152645 :	VarHandle lookup access control tests - Closed
JDK-8153870 :	Result-boxed and result-less VarHandles are significantly penalized - Resolved
JDK-8154447 :	Exempt classes under java.util.concurrent from MH.Lookup restrictions - Closed
JDK-8154556 :	Use java.nio.ByteOrder instead of boolean value - Closed
JDK-8154737 :	Rename VarHandle.compareAndExchangeVolatile to VarHandle.compareAndExchange - Resolved
JDK-8154755 :	Add a VarHandle weakCompareAndSet with volatile semantics - Resolved
JDK-8155258 :	VarHandle implementation improvements - Resolved
JDK-8155739 :	[TESTBUG] VarHandles/Unsafe tests for weakCAS should allow spurious failures - Resolved
JDK-8155965 :	Unsafe.weakCompareAndSetVolatile entry points and intrinsics - Resolved
JDK-8156068 :	Unsafe.{get\|set}Opaque should be single copy atomic - Resolved
JDK-8156485 :	MethodHandles.varHandleExactInvoker should perform exact checks - Resolved
JDK-8156486 :	Tests for invokeExact of handles produced from MethodHandles.varHandleExactInvoker - Resolved
JDK-8157171 :	Hook up Unsafe.weakCompareAndSetVolatile to VarHandles - Resolved
JDK-8157726 :	VarHandles/Unsafe should support sub-word atomic ops - Resolved
JDK-8158039 :	VarHandle float/double field/array access should support CAS/set/add atomics - Resolved
JDK-8161444 :	VarHandles should provide access bitwise atomics - Resolved
JDK-8162106 :	Remove VarHandle.addAndGet - Resolved
JDK-8162107 :	Add acquire/release variants for getAndSet and getAndAdd - Resolved
JDK-8162108 :	Rename weakCompareAndSetVolatile to weakCompareAndSet - Resolved

Description

Overall issue for the design, implementation and test of VarHandles for JEP 193: Enhanced Volatiles.

The implementation is integrated into the jdk9/dev repository.

Any follow on work may, before integration into jdk9/dev, occur in the JDK 9 sandbox with the branch:

$ hg clone http://hg.openjdk.java.net/jdk9/sandbox sandbox
$ cd sandbox/
$ sh ./get_source.sh
$ sh ./common/bin/hgforest.sh up -r JEP-193-VarHandles-branch
$ sh ./configure
$ make images

http://cr.openjdk.java.net/~psandoz/jdk9/varhandles/specdiff/overview-summary.html

Comments

The variable handle implementations for arrays will benefit from an intrinsic check index method, which helps ensure that Unsafe-based array access is similar to direct array access in terms of generated code

09-09-2015