public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32086] [4.3 Regression] 10% to 20% Performance Regression Between 4.1.3 and 4.3
Date: Mon, 10 Dec 2007 16:03:00 -0000	[thread overview]
Message-ID: <20071210160347.5057.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32086-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from dominiq at lps dot ens dot fr  2007-12-10 16:03 -------
> committed, cost model now enabled for i386.

Is it working for Intel Core2Duo? At revision 130743 and

Using built-in specs.
Target: i686-apple-darwin9
Configured with: ../gcc-4.3-work/configure --prefix=/opt/gcc/gcc4.3w
--mandir=/opt/gcc/gcc4.3w/share/man --infodir=/opt/gcc/gcc4.3w/share/info
--build=i686-apple-darwin9 --enable-languages=c,c++,fortran,objc,obj-c++,java
--with-gmp=/sw --with-libiconv-prefix=/sw --with-system-zlib
--x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
Thread model: posix
gcc version 4.3.0 20071210 (experimental) (GCC) 

for 'gfc -O3 -ffast-math -funroll-loops induct.f90' (with/without
-fvect-cost-model), the execution time is:

93.986u 0.051s 1:34.04 99.9%    0+0k 0+0io 0pf+0w

while for 'gfc -O3 -ffast-math -funroll-loops --param min-vect-loop-bound=2
induct.f90', it is:

76.345u 0.048s 1:16.39 99.9%    0+0k 0+0io 0pf+0w

If yes, the cost model should be tuned for Core2Duo. If no, did I do something
wrong with the configure?

Should I open a new PR for these questions?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32086


  parent reply	other threads:[~2007-12-10 16:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 17:10 [Bug target/32086] New: " burnus at gcc dot gnu dot org
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 [this message]
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=20071210160347.5057.qmail@sourceware.org \
    --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).