From: Jeffrey A Law <law@cygnus.com>
To: "Michael P. Hayes" <michaelh@ongaonga.chch.cri.nz>
Cc: egcs@cygnus.com
Subject: Re: Memory aliasing
Date: Sun, 26 Oct 1997 09:34:00 -0000 [thread overview]
Message-ID: <25136.877887371@hurl.cygnus.com> (raw)
In-Reply-To: <199710150031.NAA18141@ongaonga.chch.cri.nz>
In message < 199710150031.NAA18141@ongaonga.chch.cri.nz >you write:
>
> I've noticed that memrefs_conflict_p considers the following operands
> to reference conflicting memory:
>
> (mem:QI (plus:QI (reg:QI 8 ar0) (const_int 1)))
>
> (mem:QI (reg:QI 8 ar0))
Does the particular call where they're considered conflicting come
from a call chain which includes true_dependence? It appears that
true_dependence is passing in the wrong first argument when it
calls memrefs_conflict_p.
jeff
next prev parent reply other threads:[~1997-10-26 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-14 17:27 Michael P. Hayes
1997-10-26 9:34 ` Jeffrey A Law [this message]
2004-10-10 1:19 Rajkishore Barik
[not found] <20041011174109.GA1641@redhat.com>
2004-10-24 19:13 ` Rajkishore Barik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25136.877887371@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=michaelh@ongaonga.chch.cri.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).