From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31431 invoked by alias); 16 Jan 2011 08:32:57 -0000 Received: (qmail 31423 invoked by uid 22791); 16 Jan 2011 08:32:56 -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; Sun, 16 Jan 2011 08:32:52 +0000 From: "aoliva at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/45122] [4.6 Regression] -funsafe-loop-optimizations causes FAIL: gcc.c-torture/execute/pr27285.c execution X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: aoliva at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: aoliva at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: Attachment #22978 is obsolete 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: Sun, 16 Jan 2011 08:36: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-01/txt/msg01508.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45122 Alexandre Oliva changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #22978|0 |1 is obsolete| | --- Comment #8 from Alexandre Oliva 2011-01-16 08:32:33 UTC --- Created attachment 22980 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22980 Patch that fixes the problem by discarding too unsafe optimizations Oops, the first attachment was missing a refresh on the correct machine. This is the version I meant to post. The one I posted before was was abandoned approach that I had already started turning into what I meant to post, but that would print a different warning for the case of multiple exits, rather than being silent about the optimization it refused to perform.