public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38824] [4.4 Regression] performance regression of sse code from 4.2/4.3
Date: Sun, 08 Feb 2009 12:36:00 -0000	[thread overview]
Message-ID: <20090208123639.16449.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38824-12873@http.gcc.gnu.org/bugzilla/>



------- Comment #15 from hubicka at gcc dot gnu dot org  2009-02-08 12:36 -------
I tested the patch on SPECfp and core and there is not much difference.  I
guess without somehow tweaking regalloc there is not much to do about this
problem. Xuepeng, if the testcase is core2-variant sensitive, perhaps it is not
related to uops count at all? It seems to me that the bottleneck should lie
elsewhere anyway, as the testcase should be memory bound after all...

Honza


-- 


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


  parent reply	other threads:[~2009-02-08 12:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 11:25 [Bug target/38824] New: [4.4 regression] " tim at klingt dot org
2009-01-13 15:07 ` [Bug target/38824] " rguenth at gcc dot gnu dot org
2009-01-13 16:22 ` tim at klingt dot org
2009-01-14 20:20 ` hubicka at gcc dot gnu dot org
2009-01-14 20:26 ` [Bug target/38824] [4.4 Regression] " rguenth at gcc dot gnu dot org
2009-01-14 20:32 ` [Bug target/38824] [4.4 regression] " hubicka at gcc dot gnu dot org
2009-01-15  0:31 ` hubicka at gcc dot gnu dot org
2009-01-15  1:26 ` hjl dot tools at gmail dot com
2009-01-15  1:49 ` hubicka at ucw dot cz
2009-01-23 16:19 ` [Bug target/38824] [4.4 Regression] " rguenth at gcc dot gnu dot org
2009-01-24  5:12 ` xuepeng dot guo at intel dot com
2009-01-24  9:56 ` tim at klingt dot org
2009-01-24 13:14 ` tim at klingt dot org
2009-01-25 17:56 ` rguenth at gcc dot gnu dot org
2009-02-06  9:16 ` bonzini at gnu dot org
2009-02-06 22:35 ` dwarak dot rajagopal at amd dot com
2009-02-07 16:18 ` rob1weld at aol dot com
2009-02-08 12:36 ` hubicka at gcc dot gnu dot org [this message]
2009-02-08 12:40 ` hubicka at gcc dot gnu dot org
2009-02-09  9:16 ` xuepeng dot guo at intel dot com
2009-02-09 13:36 ` bonzini at gnu dot org
2009-02-09 13:38 ` bonzini at gnu dot org
2009-02-10 16:29 ` dwarak dot rajagopal at amd dot com
2009-02-10 16:39 ` bonzini at gnu dot org
2009-02-11  7:37 ` xuepeng dot guo at intel dot com
2009-02-11  8:01 ` bonzini at gnu dot org
2009-02-11  8:14 ` ubizjak at gmail dot com
2009-02-11  8:58 ` bonzini at gnu dot org
2009-02-12 15:45 ` hjl at gcc dot gnu dot org
2009-02-16  9:15 ` bonzini at gnu dot org
2009-03-12 16:01 ` hjl dot tools at gmail dot com
2009-03-12 16:08 ` hjl at gcc dot gnu dot org
2009-03-12 20:22 ` 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=20090208123639.16449.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).