On Wed, Nov 25, 2015 at 11:44 AM, Bernd Schmidt <bschm...@redhat.com> wrote: > On 11/23/2015 05:05 PM, Michael Matz wrote: >> >> >> It only does so under some conditions, amongst them if it sees a >> dominating access to the same memory of the same type (load or store) and >> size. So it doesn't introduce writes on paths that don't already contain >> a write, and hence are multi-thread safe. Or, at least, that's the >> intention. > > > Does it also ensure there's no memory barrier in between?
I don't think so. Btw, if you want to add this please add a new gimple predicate to identify "memory barrier" (any call or asm with a VDEF). Richard. > > Bernd >
