public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/29854] reload_combine looses track of uses
Date: Sat, 27 Dec 2008 12:18:00 -0000	[thread overview]
Message-ID: <20081227121648.12108.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29854-5394@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from amylaar at gcc dot gnu dot org  2008-12-27 12:16 -------
(In reply to comment #1)
> Is there a test case which shows the wrong-code
> behavior, and which can be checked against the
> new register allocator?

I don't know of any particular test case.  If you
want one, I suggest to compile the SH linux kernel
with and without the patch and diff the assemply
output of the compiler.
You could also try looking in Toshi Morita's
stress testsuite, or any other code that is heavy
with reloads and large stack frames.


-- 

amylaar at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-12-27 12:16:47
               date|                            |


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


  parent reply	other threads:[~2008-12-27 12:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 21:12 [Bug rtl-optimization/29854] New: " amylaar at gcc dot gnu dot org
2008-12-26 16:04 ` [Bug rtl-optimization/29854] " tkoenig at gcc dot gnu dot org
2008-12-27 12:18 ` amylaar at gcc dot gnu dot org [this message]
2008-12-28 16:50 ` tkoenig at gcc dot gnu dot org
2008-12-28 22:08 ` amylaar at gcc dot gnu dot org
2009-12-16 17:27 ` tkoenig 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=20081227121648.12108.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).