From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 967 invoked by alias); 21 Mar 2012 13:40:25 -0000 Received: (qmail 879 invoked by uid 22791); 21 Mar 2012 13:40:23 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,TW_CF X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Mar 2012 13:40:08 +0000 From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/52650] [4.8 Regression] FAIL: gcc.dg/torture/pr51106-2.c * (internal compiler error) Date: Wed, 21 Mar 2012 13:51: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: error-recovery, ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned 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: 2012-03/txt/msg01727.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52650 --- Comment #4 from rguenther at suse dot de 2012-03-21 13:38:28 UTC --- On Wed, 21 Mar 2012, ro at CeBiTec dot Uni-Bielefeld.DE wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52650 > > --- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE 2012-03-21 13:32:31 UTC --- > > I don't yet know if they are related. > > Now I do: I've just built a 32-bit C-only compiler on > sparc-sun-solaris2.11 at r185563 (i.e. immediately before the culprit > patch), and both the ICE in gcc.dg/torture/pr51106-2.c and the other > execution failures reported are gone. If they are related (which I doubt), removing the call to cleanup_cfg in cfgexpand.c should fix them. That's the only real change in this patch - previously the cleanup_cfg call was conditional on a present EH region tree (thus, all of these issues are latent and just require a slightly different testcase)