public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/13931] [3.4/4.0/4.1 Regression] combiner much slower on big basic blocks
Date: Sat, 08 Oct 2005 05:04:00 -0000	[thread overview]
Message-ID: <20051008050436.28541.qmail@sourceware.org> (raw)
In-Reply-To: <bug-13931-7849@http.gcc.gnu.org/bugzilla/>



------- Comment #33 from ian at airs dot com  2005-10-08 05:04 -------
I found the bug report which led to the patch which is the issue in this PR. 
It starts here:
    http://gcc.gnu.org/ml/gcc-patches/2003-05/msg00796.html
and ends with this patch:
    http://gcc.gnu.org/ml/gcc-patches/2003-05/msg01358.html

I will try to recreate this problem.  It looks like we should be able to fix
this specific type of problem without losing any speed.  We should just should
not skip adding the REG_DEAD note if we don't directly set the register.  It
actually looks like the code works that way anyhow, but with luck I will be
able to recreate the problem and figure out what is really happening.


-- 


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


       reply	other threads:[~2005-10-08  5:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-13931-7849@http.gcc.gnu.org/bugzilla/>
2005-10-08  5:04 ` ian at airs dot com [this message]
2005-10-08  5:51 ` ian at airs dot com
2005-10-10 18:19 ` ian at airs dot com
2005-10-11 23:46 ` cvs-commit at gcc dot gnu dot org
2005-10-11 23:47 ` ian at airs dot com
     [not found] <20040130124106.13931.bonzini@gcc.gnu.org>
2005-07-22 21:15 ` pinskia at gcc dot gnu dot org
2005-07-25  3:09 ` pinskia at gcc dot gnu dot org
2005-09-27  5:11 ` ian at airs dot com
2005-09-27  5:33 ` ian at airs dot com
2005-09-27 16:10 ` mmitchel 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=20051008050436.28541.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).