From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14371 invoked by alias); 20 Feb 2013 19:48:14 -0000 Received: (qmail 14081 invoked by uid 48); 20 Feb 2013 19:47:54 -0000 From: "law at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/56242] [4.8 Regression] libjava/classpath/gnu/javax/swing/text/html/parser/support/textPreProcessor.java:175:0: ICE: Segmentation fault Date: Wed, 20 Feb 2013 19:48: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-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: law at redhat dot com X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: vries at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.8.0 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2013-02/txt/msg02104.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56242 --- Comment #10 from Jeffrey A. Law 2013-02-20 19:47:53 UTC --- My first thought WRT the actual patch itself is why not put the logic to fixup the insn chain for SEQUENCEs at the end of reorder_insns_nobb? That would avoid similar problems for any other code that used this function after reorg.c had started. It also seems to me there are 4 cases that need to be fixed. FROM is a SEQUENCE Need to fix PREV_INSN of the first insn in the SEQUENCE TO is a SEQUENCE Need to fix NEXT_INSN of the last insn in the SEQUENCE PREV_INSN (FROM) is a sequence Need to fix NEXT_INSN of the last INSN in the SEQUENCE NEXT_INSN (TO) is a sequence Need to fix PREV_INSN of the first INSN in the SEQUENCE Am I missing something here?