From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 127293 invoked by alias); 19 Apr 2015 17:42:14 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 127267 invoked by uid 48); 19 Apr 2015 17:42:09 -0000 From: "vries at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg01561.txt.bz2 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.