RFR: JDK-8074578 Document memory visibility effects of some Unsafe methods

[David Holmes]

On 24/03/2015 5:55 PM, Paul Sandoz wrote:
> On Mar 24, 2015, at 12:27 AM, John Rose <john.r.rose at oracle.com> wrote:
>> Meanwhile, Paul Sandoz is working to refactor these aspects, creating a large chunk of API that will be public, portable, and secure.  You've got to sympathize with him for not wanting to run through all the inevitable arguments about concurrency primitives once for Unsafe and once again later for VarHandles.
>
> Yes, that's it. As i said i am all for it, but sensing disagreement thought it might be best to hold off a bit. I don't wanna block if that disagreement is resolved. In fact i wanna take a swing at some other aspects of Unsafe to clear up the naming of putOrdered* as mooted in an email to hotspot-runtime.

I will defer to John's wisdom on this. These discussions burn a lot of 
cycles with little concrete benefit to be gained.

David

> Paul.
>