Re: Use OEP_MATCH_SIDE_EFFECTS in ao_compare_refs

2020-11-20 Thread Richard Biener via Gcc-patches
On Fri, Nov 20, 2020 at 10:53 AM Jan Hubicka wrote: > > Hi, > As Jakub reminded me, I introduced OEP_MATCH_SIDE_EFFECTS for cases like > ICF or tail merging where we merge accesses from different code paths. > By default operand_equal_p is designed for accesses from one code path > where we do not

Use OEP_MATCH_SIDE_EFFECTS in ao_compare_refs

2020-11-20 Thread Jan Hubicka
Hi, As Jakub reminded me, I introduced OEP_MATCH_SIDE_EFFECTS for cases like ICF or tail merging where we merge accesses from different code paths. By default operand_equal_p is designed for accesses from one code path where we do not want to merge two side effects. Since compare_ao_refs is curren