public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65802] [6 Regression] ICE in redirect_eh_edge_1, at tree-eh.c:2335
Date: Sun, 19 Apr 2015 17:42:00 -0000	[thread overview]
Message-ID: <bug-65802-4-x2UiJ0tNJp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65802-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from vries at gcc dot gnu.org ---
This patch allows the example to pass:
...
diff --git a/gcc/passes.def b/gcc/passes.def
index ffa63b5..041197c 100644
--- a/gcc/passes.def
+++ b/gcc/passes.def
@@ -344,7 +344,6 @@ along with GCC; see the file COPYING3.  If not see
       NEXT_PASS (pass_tm_edges);
   POP_INSERT_PASSES ()
   NEXT_PASS (pass_vtable_verify);
-  NEXT_PASS (pass_lower_vaarg);
   NEXT_PASS (pass_lower_vector);
   NEXT_PASS (pass_lower_complex_O0);
   NEXT_PASS (pass_asan_O0);
@@ -352,6 +351,7 @@ along with GCC; see the file COPYING3.  If not see
   NEXT_PASS (pass_sanopt);
   NEXT_PASS (pass_cleanup_eh);
   NEXT_PASS (pass_lower_resx);
+  NEXT_PASS (pass_lower_vaarg);
   NEXT_PASS (pass_nrv);
   NEXT_PASS (pass_cleanup_cfg_post_optimizing);
   NEXT_PASS (pass_warn_function_noreturn);
...

I have no knowledge of the exception handling implementation, so:
1. a proper root cause analysis would take me some time.
2. I have no idea whether the patch is actually correct.  I'll try a bootstrap
   and reg-test though, that'll gives us at least more information.


  parent reply	other threads:[~2015-04-19 17:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65802-4@http.gcc.gnu.org/bugzilla/>
2015-04-19  8:59 ` vries at gcc dot gnu.org
2015-04-19 17:42 ` vries at gcc dot gnu.org [this message]
2015-04-19 21:30 ` vries at gcc dot gnu.org
2015-04-19 21:37 ` vries at gcc dot gnu.org
2015-04-20  7:23 ` vries at gcc dot gnu.org
2015-04-20  8:24 ` rguenth at gcc dot gnu.org
2015-04-20  8:42 ` vries at gcc dot gnu.org
2015-04-21  8:43 ` vries at gcc dot gnu.org
2015-04-21  8:46 ` vries at gcc dot gnu.org
2015-04-24 14:19 ` vries 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-65802-4-x2UiJ0tNJp@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).