[concurrency-interest] Unsafe publication of new objects question

Justin T. Sampson justin at krasama.com
Fri Nov 12 21:28:23 EST 2010

On Fri, Nov 12, 2010 at 2:16 PM, David Holmes <davidcholmes at aapt.net.au>
> Andrew Trick writes:
> > The JVM needs an effective store-store memory barrier between all
> > stores that initialize a new object and any store that may publish a
> > pointer to it. Not easy to do efficiently on all architectures.
> > -Andy
> The JVM would need this if it were to guarantee safe-publication, but it
> doesn't guarantee that.

It does for final fields, right? Or is that a different concept?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20101112/630c26ea/attachment.html>

More information about the Concurrency-interest mailing list