Hi, alias_sets_conflict_p are still used in various places to determine whether two memory accesses are aliased. It is based on unique set number, which seems not correct with recent changes on alias oracle. For example, in ddg.c cross-iteration memory dependence is drawn by calling insn_alias_sets_conflict_p, which in turns calls alias_sets_conflict_p and gets the wrong answer. Using rtx_refs_may_alias_p allow the ddg to be built correctly and our modulo scheduler to succeed.
Shouldn't alias_sets_conflict_p be replaced with rtx_refs_may_alias_p everywhere? What's catch? Cheers, Bingfeng
