-
Bug
-
Resolution: Fixed
-
P3
-
None
-
repo-valhalla
The current implementation supports these operations using locking. Not only this is inefficient, but atomicity guarantees can only be provided as long as all actors access the storage through the var handle (and its associated lock). That is, if thread A performs an atomic access using a var handle, but thread B just performs a plain access on the same variable, atomicity is lost.
Conservatively, we should:
* make sure that var handles pointing to flat fields only support plain modes
* non-plain access modes on array element var handles reject flat array parameters
- causes
-
JDK-8353180 [lworld] C2: Meeting two constant TypeAryPtr with different nullness is wrongly treated as exact
-
- Resolved
-
-
JDK-8353182 [lworld] C2: Multiple IR test failures in compiler/gcbarriers/TestZGCBarrierElision.java after JDK-8351569
-
- Closed
-
- relates to
-
JDK-8357245 [lworld] Potential performance regression of Unsafe::getAndSet after JDK-8351569
-
- Open
-
-
JDK-8351211 [lworld] Atomic layout access support in Unsafe
-
- Open
-
-
JDK-8352737 [lworld] Fix TestIntrinsics after VarHandle support cleanup
-
- Open
-
-
JDK-8329234 [lworld] compiler/gcbarriers/TestZGCBarrierElision.java fails after JDK-8329205
-
- In Progress
-
-
JDK-8343420 [lworld] compiler/gcbarriers/TestG1BarrierGeneration.java after merging JDK-8334060 in jdk-24+18
-
- Resolved
-
- links to
-
Commit(lworld) openjdk/valhalla/0f7cdf3b
-
Review(lworld) openjdk/valhalla/1402