-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: None
-
Component/s: core-libs
-
None
-
b154
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8174619 | 10 | Paul Sandoz | P3 | Resolved | Fixed | b01 |
The work to replace Unsafe with VarHandles with JDK-8080603 has resulted in good consolidation of the remaining Unsafe dependencies, specifically those where Thread's fields need to be accessed by ThreadLocalRandom and Striped64.
Aa Peter Levert shows it's possible to leverage SharedSecrets:
http://cr.openjdk.java.net/~plevart/misc/JavaLangThreadAccess/webrev.Striped64/
which exposes VarHandles to the Thread's appropriate fields. AN alternative is to expose Thread's Lookup in controlled manner to specific classes.
A concern is this approach may cause start-up circularities so should be investigated and tested carefully.
Aa Peter Levert shows it's possible to leverage SharedSecrets:
http://cr.openjdk.java.net/~plevart/misc/JavaLangThreadAccess/webrev.Striped64/
which exposes VarHandles to the Thread's appropriate fields. AN alternative is to expose Thread's Lookup in controlled manner to specific classes.
A concern is this approach may cause start-up circularities so should be investigated and tested carefully.
- backported by
-
JDK-8174619 Enable Thread to grant VarHandle field access to ThreadLocalRandom/Striped64
-
- Resolved
-
- relates to
-
JDK-8169069 Module system implementation refresh (11/2016)
-
- Resolved
-