[concurrency-interest] DirectByteBuffers and reachabilityFence

Andrew Haley aph at redhat.com
Wed Dec 9 14:45:56 EST 2015


On 12/09/2015 07:15 PM, Gil Tene wrote:

> Implementations can vary from an opaque non-inlineable method call
> that takes the 'this' ref as an argument, to ones that just maintain
> a USE on the exit paths that doesn't get optimized away (and as you
> note may mislead/drive the register allocator to want to keep the
> thing in a register), to ones that somehow eliminate the actual use
> and the wish to hold it in a register for that use, but prevent the
> recycling of the virtual register and/or associated stack slot.

Ah, okay, I think you're envisaging a much more major change to the
compiler than I was.  I can certainly see a way to do what you suggest
but it's a fair bit of work.

Andrew.


More information about the Concurrency-interest mailing list