public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/39837] [4.3/4.4/4.5 regression] extra spills due to RTL LICM
Date: Sat, 10 Jul 2010 21:07:00 -0000	[thread overview]
Message-ID: <20100710210723.1826.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39837-17592@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from sandra at codesourcery dot com  2010-07-10 21:07 -------
I just checked to see if this is still a problem.  As of r162042, the example
in comment #1 produces the same (bad) output as GCC 4.4.1. However, the example
in comment #4 looks fixed to me, with this output:

test:
        push    {r0, r1, r2, lr}
        mov     r3, #0
        str     r3, [sp, #4]
.L2:
        add     r0, sp, #4
        bl      func
        ldr     r3, [sp, #4]
        cmp     r3, #12
        ble     .L2
        @ sp needed for prologue
        pop     {r0, r1, r2, pc}

As it was the latter test case that caused this to be marked as a duplicate of
PR 36758, maybe the original test case is tripping over a different problem and
needs to be re-examined?


-- 


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


  parent reply	other threads:[~2010-07-10 21:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 16:44 [Bug rtl-optimization/39837] New: [4.3/4.4/4.5 regression] unoptimal code generated alexvod at google dot com
2009-04-21 16:46 ` [Bug rtl-optimization/39837] " alexvod at google dot com
2009-04-21 16:47 ` alexvod at google dot com
2009-04-21 16:49 ` pinskia at gcc dot gnu dot org
2009-04-22 13:37 ` rguenth at gcc dot gnu dot org
2009-04-23 16:40 ` alexvod at google dot com
2009-05-20 14:17 ` ramana at gcc dot gnu dot org
2009-08-04 12:49 ` [Bug rtl-optimization/39837] [4.3/4.4/4.5 regression] extra spills due to RTL LICM rguenth at gcc dot gnu dot org
2010-01-02  0:42 ` steven at gcc dot gnu dot org
2010-01-29 23:11 ` steven at gcc dot gnu dot org
2010-01-30  9:47 ` rakdver at kam dot mff dot cuni dot cz
2010-03-02 19:59 ` pinskia at gcc dot gnu dot org
2010-03-02 20:10 ` pinskia at gcc dot gnu dot org
2010-07-10 21:07 ` sandra at codesourcery dot com [this message]
2010-07-11  7:51 ` bonzini at gnu dot org
2010-07-11 11:40 ` steven at gcc dot gnu dot org
2010-07-11 17:47 ` sandra at codesourcery dot com
2010-07-11 22:48 ` steven at gcc dot gnu dot org
2010-07-11 22:55 ` steven at gcc dot gnu dot org
2010-07-13 17:13 ` sandra at codesourcery dot com
     [not found] <bug-39837-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 14:57 ` 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=20100710210723.1826.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).