[concurrency-interest] DirectByteBuffers and reachabilityFence

Andrew Haley aph at redhat.com
Tue Dec 8 04:50:08 EST 2015

On 07/12/15 15:20, Vitaly Davidovich wrote:
> If reachabilityFence use is going to proliferate, especially in perf
> sensitive places, Hotspot will need to make this method simply a
> liveness marker and not emit a call like the current
> prototype/version is doing.

Perhaps, but we've already discussed that, and it's not so hard.
Surely correctness comes first, then we optimize.  I expect we're
going to need a reachabilityFence in many (almost all?) methods of
classes with finalizers.


More information about the Concurrency-interest mailing list