This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/50904] [4.7 regression] pessimization when -fno-protect-parens is enabled by -Ofast
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 02 Dec 2011 14:40:48 +0000
- Subject: [Bug rtl-optimization/50904] [4.7 regression] pessimization when -fno-protect-parens is enabled by -Ofast
- Auto-submitted: auto-generated
- References: <bug-50904-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50904
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|burnus@net-b.de |dominiq at lps dot ens.fr
--- Comment #25 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-12-02 14:40:48 UTC ---
(In reply to comment #24)
> Every program that would break with non honoring explicit parantheses
> would also break if the bracketed expression would be explicitely
> computed into a temporary (without explicit parantheses). So it
> should be easy to construct a testcase if you have one that breaks
> without -fno-protect-parens.
I vaguely recall that one of the Polyhedron benchmarks gets minutely out of the
correctness-check tolerance range with -fno-protect-parens while it stays
within without. I think Dominique has a program where the effect is more
disastrous.