[concurrency-interest] DirectByteBuffers and reachabilityFence

Vitaly Davidovich vitalyd at gmail.com
Thu Dec 10 18:47:19 EST 2015


So frankly, I can no longer tell whether this is correct or not, and if
it's correct, only because a JLS update slipped through the cracks.  Did we
net out somewhere?

sent from my phone
On Dec 10, 2015 6:37 PM, "David Holmes" <davidcholmes at aapt.net.au> wrote:

> To be 100% clear: hotspot does not implement the requirement that an
> object is only eligible for finalization after its constructors have
> completed. Instead it makes them eligible for finalization at the
> successful end of Object.<init> (by default – if RegisterFinalizersAtInit
> is false then it will register them at the end of allocation instead).
>
>
>
> David
>
>
>
> *From:* Vitaly Davidovich [mailto:vitalyd at gmail.com]
> *Sent:* Friday, December 11, 2015 9:19 AM
> *To:* dholmes at ieee.org
> *Cc:* concurrency-interest at cs.oswego.edu; David M. Lloyd
> *Subject:* Re: [concurrency-interest] DirectByteBuffers and
> reachabilityFence
>
>
>
> sent from my phone
> On Dec 10, 2015 4:36 PM, "David Holmes" <davidcholmes at aapt.net.au> wrote:
> >
> > David M. Lloyd writes:
> > >
> > > On 12/09/2015 07:44 PM, David Holmes wrote:
> > > > To be clear, I missed this later assertion:
> > > >
> > > >> In summary, we agree that an object can _become finalizable_ before
> > > >> completion of its constructor, if the Object constructor completed
> > > >> normally and the object is otherwise no longer reachable.
> > > >
> > > > No! The object should not be able to become finalizable until after
> > > all its
> > > > constructors have completed, and then it becomes unreachable.
> > >
> > > Is this your view of the existing world, or what you are proposing be
> > > changed?  I'm losing track of what's what in this discussion. :-)
> >
> > This is how the existing world should have been if the JLS update had not
> > been snafu'd. Justin would argue it should be the current state
> regardless
> > due to happens-before definition. Regardless the JVM does not currently
> > implement this.
>
> To avoid further confusion, the JVM (I'm assuming you mean Hotspot)
> doesn't implement what exactly?
>
> >
> > David H.
> >
> >
> > > --
> > > - DML
> > > _______________________________________________
> > > Concurrency-interest mailing list
> > > Concurrency-interest at cs.oswego.edu
> > > http://cs.oswego.edu/mailman/listinfo/concurrency-interest
> >
> > _______________________________________________
> > Concurrency-interest mailing list
> > Concurrency-interest at cs.oswego.edu
> > http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20151210/af4041b9/attachment.html>


More information about the Concurrency-interest mailing list