This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Shouldn't alias_sets_conflict_p be replaced with rtx_refs_may_alias_p?
- From: Steven Bosscher <stevenb dot gcc at gmail dot com>
- To: Bingfeng Mei <bmei at broadcom dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Richard Guenther <richard dot guenther at gmail dot com>
- Date: Wed, 4 Aug 2010 17:26:27 +0200
- Subject: Re: Shouldn't alias_sets_conflict_p be replaced with rtx_refs_may_alias_p?
- References: <7FB04A5C213E9943A72EE127DB74F0ADA68997565C@SJEXCHCCR02.corp.ad.broadcom.com>
On Wed, Aug 4, 2010 at 2:02 PM, Bingfeng Mei <bmei@broadcom.com> wrote:
> 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.
Just to clarify: When you say "wrong", do you mean "incorrect" or "too
conservative"?
Ciao!
Steven