This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/50182] Performance degradation from gcc 4.1 (x86_64)
- From: "oleg at smolsky dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 02 Mar 2012 08:21:41 +0000
- Subject: [Bug target/50182] Performance degradation from gcc 4.1 (x86_64)
- Auto-submitted: auto-generated
- References: <bug-50182-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50182
--- Comment #31 from oleg at smolsky dot net 2012-03-02 08:21:41 UTC ---
I don't think there is a need to actually check the result in this
benchmarkable fragment, so that will reduce the code a little. The only
thing that I was hitting is about fooling/forcing the compiler not to
discard the intermediate result and actually perform every calculation
and iteration :)
Let me try do digest this further. I'll also get you a result from our
production compiler (v4.1 that emits the fastest code)