From: Richard Henderson <rth@redhat.com>
To: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: REQ_EQUAL and mems hoisted out of loops
Date: Fri, 28 Mar 2003 02:12:00 -0000 [thread overview]
Message-ID: <20030327234908.GJ30577@redhat.com> (raw)
In-Reply-To: <20030326084933.GU931@bubble.sa.bigpond.net.au>
On Wed, Mar 26, 2003 at 07:19:33PM +1030, Alan Modra wrote:
> (load_mems): Remove invalid REG_EQUAL notes after hoisting.
I think this is the wrong spot to handle this.
Do it in replace_loop_mems instead.
r~
prev parent reply other threads:[~2003-03-27 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 14:02 Alan Modra
2003-03-25 18:27 ` David Edelsohn
2003-03-26 10:36 ` Alan Modra
2003-03-26 17:26 ` Matt Kraai
2003-03-28 2:12 ` Richard Henderson [this message]
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=20030327234908.GJ30577@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/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).