Remove noce_mem_write_may_trap_or_fault_p in ifcvt
Bernd Schmidt
bschmidt@redhat.com
Wed Nov 25 10:46:00 GMT 2015
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?
Bernd
More information about the Gcc-patches
mailing list