public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/28868] [4.3/4.4/4.5 Regression] Not eliminating the PHIs which have the same arguments
Date: Sat, 04 Apr 2009 17:57:00 -0000	[thread overview]
Message-ID: <20090404175740.5234.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28868-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #18 from rguenth at gcc dot gnu dot org  2009-04-04 17:57 -------
Patch posted:
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg00311.html

it will replace redundant PHI nodes with a copy, so

<bb 4>:
  # c_1 = PHI <a_4(D)(2), b_7(D)(3)>
  # d_2 = PHI <a_4(D)(2), b_7(D)(3)>
  D.1599_10 = c_1 + d_2;

will become

<bb 4>:
  # c_1 = PHI <a_4(D)(2), b_7(D)(3)>
  d_2 = c_1
  D.1599_10 = c_1 + d_2;

to not immediately trigger PR23821 (of course the next copyprop will
happily propagate c_1 into all uses of d_2).  It does replace single-uses
though, which does not increase register pressure.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28868


  parent reply	other threads:[~2009-04-04 17:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28  5:52 [Bug tree-optimization/28868] New: Not elimintation the PHIs which have the same agruments pinskia at gcc dot gnu dot org
2006-08-28  5:54 ` [Bug tree-optimization/28868] " pinskia at gcc dot gnu dot org
2006-08-28  6:01 ` [Bug tree-optimization/28868] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-08-28  6:06 ` pinskia at gcc dot gnu dot org
2006-08-28  6:43 ` pinskia at gcc dot gnu dot org
2006-08-28 13:59 ` steven at gcc dot gnu dot org
2006-08-28 14:37 ` pinskia at gcc dot gnu dot org
2006-08-29  5:51 ` steven at gcc dot gnu dot org
2006-08-29 14:59 ` [Bug tree-optimization/28868] [4.0/4.1/4.2 Regression] Not elimintating " dberlin at gcc dot gnu dot org
2006-08-30  4:44 ` pinskia at gcc dot gnu dot org
2006-09-01 22:09 ` mmitchel at gcc dot gnu dot org
2007-02-03 19:38 ` [Bug tree-optimization/28868] [4.0/4.1/4.2/4.3 Regression] Not elimintating the PHIs which have the same arguments gdr at gcc dot gnu dot org
2007-02-03 20:55 ` pinskia at gcc dot gnu dot org
2007-02-14  9:16 ` mmitchel at gcc dot gnu dot org
2007-07-01  1:09 ` pinskia at gcc dot gnu dot org
2007-11-04 15:46 ` rguenth at gcc dot gnu dot org
2007-11-04 19:24 ` dberlin at dberlin dot org
2007-11-05  6:13 ` [Bug tree-optimization/28868] [4.0/4.1/4.2/4.3 Regression] Not eliminating " sebpop at gmail dot com
2008-07-04 21:29 ` [Bug tree-optimization/28868] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-02-04  7:40 ` bonzini at gnu dot org
2009-02-04 10:15 ` rguenth at gcc dot gnu dot org
2009-03-25 13:18 ` rguenth at gcc dot gnu dot org
2009-03-31 19:41 ` [Bug tree-optimization/28868] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-04-04 17:57 ` rguenth at gcc dot gnu dot org [this message]
2009-04-06 14:56 ` [Bug tree-optimization/28868] [4.3/4.4 " rguenth at gcc dot gnu dot org
2009-04-06 14:56 ` [Bug tree-optimization/28868] [4.3/4.4/4.5 " rguenth at gcc dot gnu dot org
2009-08-04 12:36 ` [Bug tree-optimization/28868] [4.3/4.4 " rguenth at gcc dot gnu dot org
2010-02-26  1:34 ` law at redhat dot com
2010-02-26 11:05 ` rguenth at gcc dot gnu dot org

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=20090404175740.5234.qmail@sourceware.org \
    --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).