public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51042] [4.5/4.6/4.7 Regression] endless recursion in phi_translate
Date: Wed, 09 Nov 2011 14:43:00 -0000	[thread overview]
Message-ID: <bug-51042-4-VkcS4OQGHT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51042-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-11-09 14:33:14 UTC ---
The clean () code does not work properly for memory references it seems.  We
fail to prune expressions that are not available (the tricks we play with
dominance tests for virtual operands are not effective once we translate
them).


  parent reply	other threads:[~2011-11-09 14:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 23:01 [Bug c/51042] New: segfault regehr at cs dot utah.edu
2011-11-09  9:15 ` [Bug tree-optimization/51042] [4.7 Regression] endless recursion in phi_translate jakub at gcc dot gnu.org
2011-11-09  9:39 ` [Bug tree-optimization/51042] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2011-11-09 13:26 ` rguenth at gcc dot gnu.org
2011-11-09 14:43 ` rguenth at gcc dot gnu.org [this message]
2011-11-10 13:10 ` rguenth at gcc dot gnu.org
2011-11-10 15:37 ` rguenth at gcc dot gnu.org
2011-11-10 15:54 ` [Bug tree-optimization/51042] [4.5/4.6 " rguenth at gcc dot gnu.org
2012-01-03 14:47 ` rguenth at gcc dot gnu.org
2012-06-12  9:54 ` [Bug tree-optimization/51042] [4.5 " liujiangning at gcc dot gnu.org
2012-06-20 13:08 ` rguenth at gcc dot gnu.org
2012-07-02 10:16 ` rguenth at gcc dot gnu.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=bug-51042-4-VkcS4OQGHT@http.gcc.gnu.org/bugzilla/ \
    --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).