From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21787 invoked by alias); 11 Mar 2011 04:42:34 -0000 Received: (qmail 21775 invoked by uid 22791); 11 Mar 2011 04:42:32 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 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; Fri, 11 Mar 2011 04:42:28 +0000 From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/45962] [4.6 Regression]: many c/c++ failures on cris-elf, in r165236:165242 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: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: rth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: Status Resolution 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 Date: Fri, 11 Mar 2011 04:42: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 X-SW-Source: 2011-03/txt/msg01085.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45962 Hans-Peter Nilsson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #19 from Hans-Peter Nilsson 2011-03-11 04:42:21 UTC --- (In reply to comment #18) > > To be investigated; I'll do my part. Famous last words... well, it didn't happen yet, but something else happened: This bug was either fixed or re-covered in the range 170660..170665 and I'd be very surprised if it wasn't your 170663. Tracking down the related mailing list conversations (with DJ regarding m32r) it was apparently a fix intended for exactly this problem, so thanks. :] Yay, no regressions since T0. Did I mention I tried at the previous iteration setting EXIT_IGNORE_STACK to 1 and got massive regressions? Ripe for a revisit. Just not now. As an intended fix was committed, I'm closing this PR.