public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30735]  New: 50% slow down due to mem-ssa merge
Date: Thu, 08 Feb 2007 16:58:00 -0000	[thread overview]
Message-ID: <bug-30735-682@http.gcc.gnu.org/bugzilla/> (raw)

There is a huge regression of gcc 4.3 performance detected on
cpu2006/454.calculix benchmark at -O2 optimization level on
x86_64-redhat-linux.

Regression is caused by mem-ssa merge 12/12/2006 (revision 119760).
http://gcc.gnu.org/viewcvs?view=rev&revision=119760

mem-ssa merge may introduce unnecessary memory <-> register moves.


-- 
           Summary: 50% slow down due to mem-ssa merge
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hjl at lucon dot org


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


             reply	other threads:[~2007-02-08 16:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 16:58 hjl at lucon dot org [this message]
2007-02-08 17:01 ` [Bug tree-optimization/30735] " hjl at lucon dot org
2007-02-08 17:08 ` rguenth at gcc dot gnu dot org
2007-02-08 17:13 ` hjl at lucon dot org
2007-02-08 18:42 ` dnovillo at gcc dot gnu dot org
2007-02-13  0:59 ` dnovillo at gcc dot gnu dot org
2007-02-15 23:37 ` pthaugen at us dot ibm dot com
2007-03-07  0:44 ` [Bug tree-optimization/30735] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-04-11 16:14 ` dnovillo at gcc dot gnu dot org
2007-06-29 17:52 ` mmitchel at gcc dot gnu dot org
2007-06-29 17:57 ` hjl at lucon dot org
2007-11-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-30735-682@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).