public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/14758] [tree-ssa] another missed forward propagation opportunity
Date: Wed, 31 Mar 2004 00:02:00 -0000 [thread overview]
Message-ID: <20040331000252.1049.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040328015408.14758.kazu@cs.umass.edu>
------- Additional Comments From dnovillo at redhat dot com 2004-03-31 00:02 -------
Subject: Re: [tree-ssa] another missed forward
propagation opportunity
On Tue, 2004-03-30 at 15:30, pinskia at gcc dot gnu dot org wrote:
> I am going to take care of this one.
>
Andrew, I'm planning to generalize CCPs propagation engine after the
merge into mainline. Long term, the forward propagation pass will
probably be subsumed by this.
At this point I'm not sure if it's even worth our time trying to extend
it to handle more cases.
Diego.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14758
next prev parent reply other threads:[~2004-03-31 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 1:54 [Bug optimization/14758] New: " kazu at cs dot umass dot edu
2004-03-28 7:35 ` [Bug optimization/14758] " pinskia at gcc dot gnu dot org
2004-03-30 20:30 ` pinskia at gcc dot gnu dot org
2004-03-30 21:31 ` pinskia at gcc dot gnu dot org
2004-03-30 21:35 ` pinskia at gcc dot gnu dot org
2004-03-31 0:02 ` dnovillo at redhat dot com [this message]
2004-03-31 0:04 ` pinskia at gcc dot gnu dot org
2004-03-31 5:36 ` pinskia at gcc dot gnu dot org
2004-05-15 6:05 ` [Bug tree-optimization/14758] " pinskia at gcc dot gnu dot org
2004-05-15 15:46 ` giovannibajo at libero dot it
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=20040331000252.1049.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).