This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/53239] [4.7/4.8 Regression] VRP vs named value return opt
- From: "dak at gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 07 May 2012 13:31:03 +0000
- Subject: [Bug tree-optimization/53239] [4.7/4.8 Regression] VRP vs named value return opt
- Auto-submitted: auto-generated
- References: <bug-53239-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53239
David Kastrup <dak at gnu dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dak at gnu dot org
--- Comment #12 from David Kastrup <dak at gnu dot org> 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.