public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin@mpa-garching.mpg.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/47167] Performance regression in numerical code
Date: Wed, 19 Jan 2011 18:10:00 -0000	[thread overview]
Message-ID: <bug-47167-4-wrNaxBJPX3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47167-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Martin Reinecke <martin@mpa-garching.mpg.de> 2011-01-19 17:26:31 UTC ---
(In reply to comment #8)
> Can you check if the following patch solves your problem?

Yes, this patch gets performance back to normal on the 4.5 branch and on trunk.
Great!

> The differences in GIMPLE of the patch do not explain the code-differences
> though, so it might be just bad luck that the patch regressed things for
> you.  I can see other unwanted differences though.

I would of course be happy if the code generation would be less "erratic", and
if the nice performance I'm seeing does not depend on my luck ;)
So if I can do anything to help optimizing this kind of code more consistently,
please let me know! Of course, I'm more into numerics than into compiler
writing ...


  parent reply	other threads:[~2011-01-19 17:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 14:45 [Bug other/47167] New: " martin@mpa-garching.mpg.de
2011-01-05 14:46 ` [Bug other/47167] " martin@mpa-garching.mpg.de
2011-01-05 17:38 ` ubizjak at gmail dot com
2011-01-05 19:50 ` ubizjak at gmail dot com
2011-01-05 20:09 ` ubizjak at gmail dot com
2011-01-05 22:14 ` hjl.tools at gmail dot com
2011-01-06  9:33 ` ubizjak at gmail dot com
2011-01-19 15:37 ` martin@mpa-garching.mpg.de
2011-01-19 16:32 ` rguenth at gcc dot gnu.org
2011-01-19 18:10 ` martin@mpa-garching.mpg.de [this message]
2011-01-20 10:41 ` rguenth at gcc dot gnu.org
2011-01-20 10:42 ` rguenth at gcc dot gnu.org
2011-01-20 10:43 ` rguenth at gcc dot gnu.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-47167-4-wrNaxBJPX3@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).