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/62079] [4.9/5 Regression] ICE: in calc_dfs_tree, at dominance.c:401 with -fnon-call-exceptions
Date: Wed, 13 Aug 2014 14:04:00 -0000	[thread overview]
Message-ID: <bug-62079-4-QjoNct3Pb2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62079-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62079

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bernds at gcc dot gnu.org

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Funny that peep2s peep2_do_cleanup_cfg variable is write-only.  Bernd
introduced that, a simple

Index: recog.c
===================================================================
--- recog.c     (revision 213909)
+++ recog.c     (working copy)
@@ -3553,6 +3553,8 @@ peephole2_optimize (void)
   BITMAP_FREE (live);
   if (peep2_do_rebuild_jump_labels)
     rebuild_jump_labels (get_insns ());
+  if (peep2_do_cleanup_cfg)
+    cleanup_cfg (CLEANUP_CFG_CHANGED);
 }
 #endif /* HAVE_peephole2 */

fixes the testcase.


  parent reply	other threads:[~2014-08-13 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 10:13 [Bug tree-optimization/62079] New: [4.9/4.10 " zsojka at seznam dot cz
2014-08-11  8:49 ` [Bug tree-optimization/62079] " rguenth at gcc dot gnu.org
2014-08-13 13:17 ` [Bug tree-optimization/62079] [4.9/5 " rguenth at gcc dot gnu.org
2014-08-13 14:04 ` rguenth at gcc dot gnu.org [this message]
2014-08-14  8:57 ` [Bug tree-optimization/62079] [4.9 " rguenth at gcc dot gnu.org
2014-08-14  8:57 ` rguenth at gcc dot gnu.org
2014-09-09 11:43 ` rguenth at gcc dot gnu.org
2014-09-09 11:43 ` 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-62079-4-QjoNct3Pb2@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).