[concurrency-interest] Here's why Atomic*FieldReference access checking is broken
vladimir.x.ivanov at oracle.com
Wed Oct 8 11:41:37 EDT 2014
> Just by moving the nested
> AtomicIntegerFieldUpdater.AtomicIntegerFieldUpdaterImpl class to
> java.lang.invoke package, annotating the final instance fields 'tclass',
> 'cclass' and 'offset' with @Stable annotation and simplifying the
> invocation check, I get the same benchmark results. Why are those JVM
> pearls so hidden in the java.lang.invoke package?
Mostly because they are not ready for prime time yet.
There's a draft proposal for "lazy final" fields , but it hasn't been
submitted officially yet. It covers part of the functionality provided
by @Stable (fields, but not arrays).
> Now let me try to get something similar from AtomicReferenceFieldUpdater...
> Regards, Peter
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
More information about the Concurrency-interest