> Full testing still underway, but I expect it to pass.
Can you also update the comment before the function, please? It now reads:
/* Read dependence: X is read after read in MEM takes place. There can
only be a dependence here if both reads are volatile. */
But that's no longer true after
On Fri, Aug 31, 2012 at 6:51 PM, Richard Henderson wrote:
> Fixed as follows. This seems to be the only entry point in alias.c that
> didn't take ALIAS_SET_MEMORY_BARRIER into account. Getting the above into a
> test case is tricky, and I havn't figured out how to match it.
>
> Full testing st
On 2012-08-31 05:48, Andrew MacLeod wrote:
> On 08/30/2012 07:04 PM, Richard Henderson wrote:
>> Actually, we already have a memory barrier feature in rtl:
>>
>>ALIAS_SET_MEMORY_BARRIER
>>
>> but since we already set that in get_builtin_sync_mem, we'll need
>> to figure out why that's no longer
