public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/37948] [4.4 Regression] IRA generates slower code for -mtune=core2
Date: Wed, 29 Oct 2008 13:08:00 -0000	[thread overview]
Message-ID: <20081029130805.2459.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37948-682@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from hjl dot tools at gmail dot com  2008-10-29 13:08 -------
(In reply to comment #2)
> Subject: Re:  [4.4 Regression] IRA generates slower
>  code for -mtune=core2
> 
> hjl dot tools at gmail dot com wrote:
> > ------- Comment #1 from hjl dot tools at gmail dot com  2008-10-29 05:44 -------
> > It looks like the cost of loading/storing FP values aren't appropriate for
> > Core 2. With this patch:
> 
> Good.  Is regmove still helping (which would be the wrong thing to do,
> but gives a data point)?
> 
> Paolo
> 

For this bug, regmove has mixed impacts with updated core2_cost:

[hjl@gnu-6 regmove]$ ../xgcc -B../ -m32 -O2 /tmp/foo.c -o core2.sse
-mtune=core2  -msse3 -mfpmath=sse
[hjl@gnu-6 regmove]$ ../xgcc -B../ -m32 -O2 /tmp/foo.c -o o2.sse   -msse3
-mfpmath=sse
[hjl@gnu-6 regmove]$ ../xgcc -B../ -m32 -O2 /tmp/foo.c -o core2 -mtune=core2   
[hjl@gnu-6 regmove]$ ../xgcc -B../ -m32 -O2 /tmp/foo.c -o o2
[hjl@gnu-6 regmove]$ time ./o2

real    0m7.995s
user    0m7.956s
sys     0m0.003s
[hjl@gnu-6 regmove]$ time ./core2

real    0m7.951s
user    0m7.950s
sys     0m0.000s
[hjl@gnu-6 regmove]$ time ./core2.sse

real    0m7.358s
user    0m7.357s
sys     0m0.000s
[hjl@gnu-6 regmove]$ time ./o2.sse

real    0m7.177s
user    0m7.176s
sys     0m0.000s
[hjl@gnu-6 regmove]$


-- 


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


  parent reply	other threads:[~2008-10-29 13:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  5:39 [Bug rtl-optimization/37948] New: " hjl dot tools at gmail dot com
2008-10-29  5:46 ` [Bug rtl-optimization/37948] " hjl dot tools at gmail dot com
2008-10-29  7:18 ` bonzini at gnu dot org
2008-10-29  7:25   ` Andrew Thomas Pinski
2008-10-29  7:26 ` pinskia at gmail dot com
2008-10-29 13:08 ` hjl dot tools at gmail dot com [this message]
2008-10-29 14:50 ` rguenth at gcc dot gnu dot org
2008-10-30 21:08 ` rguenth at gcc dot gnu dot org
2008-10-30 22:53 ` hjl dot tools at gmail dot com
2008-11-04 19:37 ` [Bug rtl-optimization/37948] [4.4 Regression] IRA generates slower code hjl dot tools at gmail dot com
2008-11-10 16:13 ` vmakarov at redhat dot com
2008-11-10 23:24 ` vmakarov at gcc dot gnu dot org
2008-11-11  0:02 ` hjl at gcc dot gnu dot org
2008-12-06 22:07 ` steven at gcc dot gnu dot org
2008-12-10  3:03 ` Joey dot ye at intel dot com
2008-12-10  5:04 ` hjl dot tools at gmail dot com

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=20081029130805.2459.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).