From: Diego Novillo <dnovillo@google.com>
To: Dorit Nuzman <DORIT@il.ibm.com>
Cc: Ira Rosen <IRAR@il.ibm.com>,
gcc-patches@gnu.org, dberlin@dberlin.org,
dvorakz@suse.cz
Subject: Re: [patch] Remove redundant calls to copy_virtual_operands
Date: Tue, 07 Aug 2007 13:23:00 -0000 [thread overview]
Message-ID: <46B8723C.60007@google.com> (raw)
In-Reply-To: <OFEC28E137.8C9E6009-ONC2257330.004675DC-C2257330.00481FC7@il.ibm.com>
On 8/7/07 9:07 AM, Dorit Nuzman wrote:
> it looks ok to me, but it would be much better if one of the aliasing/vops
> experts took a look
Yeah, it is OK. As I mentioned earlier, I would only suggest doing
compile-time tests. Though if this fixes ICEs, then it's really better
even if a tad slower. Leaving this to update_ssa is certainly easier to
maintain.
next prev parent reply other threads:[~2007-08-07 13:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 12:10 Ira Rosen
2007-08-07 13:06 ` Dorit Nuzman
2007-08-07 13:23 ` Diego Novillo [this message]
2007-08-08 8:02 ` Ira Rosen
2007-08-08 12:06 ` Diego Novillo
2007-08-08 9:41 ` Zdenek Dvorak
2007-08-08 11:04 ` Ira Rosen
2007-08-12 19:40 ` Zdenek Dvorak
2007-08-07 13:22 ` Diego Novillo
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=46B8723C.60007@google.com \
--to=dnovillo@google.com \
--cc=DORIT@il.ibm.com \
--cc=IRAR@il.ibm.com \
--cc=dberlin@dberlin.org \
--cc=dvorakz@suse.cz \
--cc=gcc-patches@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).