From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13131 invoked by alias); 7 May 2012 13:33:02 -0000 Received: (qmail 13115 invoked by uid 22791); 7 May 2012 13:33:01 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED 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; Mon, 07 May 2012 13:32:49 +0000 From: "dak at gnu dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/53239] [4.7/4.8 Regression] VRP vs named value return opt Date: Mon, 07 May 2012 13:33:00 -0000 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: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: dak at gnu dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.7.1 X-Bugzilla-Changed-Fields: CC 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-05/txt/msg00771.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53239 David Kastrup changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dak at gnu dot org --- Comment #12 from David Kastrup 2012-05-07 13:31:03 UTC --- Unrelated question: this kind of code is quite common in connection with user-defined arithmetic classes. While I understand that changing the bug priority from "P3 normal" will likely do nothing with regard to which releases of gcc the fix will appear in, it might make a difference for distributors that tend to cherry-pick important fixes ahead of regular releases. For example, the next release of Fedora is slated to be delivered using gcc 4.7.0, and its miscompilation of LilyPond, a bonafide application, was what triggered this report. Given that the triggering pattern is quite typical for C++ and the problem being present on all architectures, it might make sense to adjust the priority.