Hi, On Wed, 25 Nov 2015, Bernd Schmidt 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? Yes. Whenever it sees any unknown call (including mem barriers) it forgets all known mem accesses (and hence can't mark accesses further down as not trapping). Ciao, Michael.
