public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32086] New: 10% to 20% Performance Regression Between 4.1.3 and 4.3
Date: Fri, 25 May 2007 17:10:00 -0000 [thread overview]
Message-ID: <bug-32086-13404@http.gcc.gnu.org/bugzilla/> (raw)
The program induct.f90 of the Polyhedron testsuite,
http://www.polyhedron.co.uk/pb05/polyhedron_benchmark_suite.html, runs about
10% slower under 4.3 than under 4.1.3 (20070430 prerelease SUSE Linux).
A cut-down testcase "test2.f90 (attachment 13611 of PR 32084) shows the same
result. At least for the testcase, the original tree is almost identical for
4.3 and 4.1.3 which means that the difference must be the middle or backend.
Timings (w/o "volatile"):
a) gfortran -march=opteron -ffast-math -funroll-loops -ftree-vectorize
-ftree-loop-linear -msse3 -O3
induct.f90: 51.65 [100%] vs 46.94 [ 90%] for gfortran 4.3 vs. 4.1.3
test2.f90: 4.60 [100%] vs 4.18 [ 91%]
b) gfortran -m32 -march=opteron -ffast-math -funroll-loops -ftree-vectorize
-ftree-loop-linear -O3
induct.f90: 61.41 [100%] vs 46.94 [ 76%]
test2.f90: 5.45 [100%] vs 4.54 [ 83%]
c) gfortran -m32 -march=opteron -ffast-math -funroll-loops -ftree-vectorize
-ftree-loop-linear -msse3 -mfpmath=sse -O3
induct.f90: 46.12 [100%] vs 46.94 [102%] (4.3 is better :-)
test2.f90: 4.14 [100%] vs 3.96 [ 96%]
(For the other polyhedron test cases, the performance loss is less: tfft 4%
slower, protein 3%, doduc 3%, channel 2%; in total 4.3 is faster, for fatigue
4.1.3 takes twice as long as 4.3. See:
http://physik.fu-berlin.de/~tburnus/gcc-trunk/benchmark/#rt)
--
Summary: 10% to 20% Performance Regression Between 4.1.3 and 4.3
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org
GCC target triplet: x86_64-unknown-linux-gnu
OtherBugsDependingO 32084
nThis:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32086
next reply other threads:[~2007-05-25 17:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 17:10 burnus at gcc dot gnu dot org [this message]
2007-09-11 11:57 ` [Bug target/32086] [4.3 Regression] " jsm28 at gcc dot gnu dot org
2007-10-10 17:45 ` mmitchel at gcc dot gnu dot org
2007-11-29 8:09 ` ubizjak at gmail dot com
2007-11-30 5:41 ` bonzini at gnu dot org
2007-11-30 6:42 ` ubizjak at gmail dot com
2007-11-30 7:17 ` bonzini at gnu dot org
2007-11-30 10:27 ` ubizjak at gmail dot com
2007-11-30 10:59 ` bonzini at gnu dot org
2007-11-30 13:20 ` ubizjak at gmail dot com
2007-11-30 13:30 ` bonzini at gnu dot org
2007-11-30 15:23 ` dominiq at lps dot ens dot fr
2007-12-10 8:35 ` bonzini at gcc dot gnu dot org
2007-12-10 8:37 ` bonzini at gnu dot org
2007-12-10 16:03 ` dominiq at lps dot ens dot fr
2007-12-10 16:38 ` bonzini at gnu dot org
2007-12-10 16:41 ` howarth at nitro dot med dot uc dot edu
2007-12-10 17:07 ` rguenth at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-32086-13404@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).