From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50449 invoked by alias); 2 Mar 2015 21:41:00 -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 50192 invoked by uid 48); 2 Mar 2015 21:40:57 -0000 From: "law at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/65233] [5 Regression] ICE (segfault) on arm-linux-gnueabihf and aarch64-linux-gnu Date: Mon, 02 Mar 2015 21:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: law at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 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-03/txt/msg00204.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65233 --- Comment #19 from Jeffrey A. Law --- Right. That's the last step for updating the CFG for a series of jump threads. It's certainly the case that the redirections can leave unreachable blocks. But the first thing that the cfg cleanup routines ought to be doing is removing those unreachable blocks -- before we call any of the block merging code. That happens in cleanup_tree_cfg_noloop. So I'd be real interested to know if we have any unreachable blocks in the CFG after cleanup_tree_cfg_noloop has completed.