public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/40783] inefficient code to accumulate function return values
Date: Mon, 27 Jul 2009 15:05:00 -0000	[thread overview]
Message-ID: <20090727150521.723.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40783-17659@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from ramana at gcc dot gnu dot org  2009-07-27 15:05 -------
This seems to be related to the other reassoc + register pressure bugs reported
in the database. I am not sure if this is a dup of either PR28481 or PR27855
but they appear to be related.

With -fno-tree-reassoc I get the same code for both loops.

time_math:
        push    {r4, r5, r6, lr}
        bl      dumm
        mov     r4, #0
        mov     r6, #99
        add     r5, r0, #0
.L2:
        add     r0, r5, #0
        bl      __aeabi_f2iz
        add     r5, r5, #1
        add     r4, r4, r0
        add     r0, r5, #0
        bl      __aeabi_f2iz
        add     r5, r5, #1
        add     r4, r4, r0
        add     r0, r5, #0
        bl      __aeabi_f2iz
        add     r5, r5, #1
        add     r4, r4, r0
        add     r0, r5, #0
        bl      __aeabi_f2iz
        add     r5, r5, #1
        add     r4, r4, r0
        sub     r6, r6, #1
        bcs     .L2
        bl      dumm
        mov     r6, #99
        add     r5, r0, #0
.L3:
        add     r0, r5, #0
        bl      MyConvert
        add     r5, r5, #1
        add     r4, r4, r0
        add     r0, r5, #0
        bl      MyConvert
        add     r5, r5, #1
        add     r4, r4, r0
        add     r0, r5, #0
        bl      MyConvert
        add     r5, r5, #1
        add     r4, r4, r0
        add     r0, r5, #0
        bl      MyConvert
        add     r5, r5, #1
        add     r4, r4, r0
        sub     r6, r6, #1
        bcs     .L3
        mov     r0, r4
        @ sp needed for prologue
        pop     {r4, r5, r6, pc}
        .size   time_math, .-time_math
        .ident  "GCC: (GNU) 4.5.0 20090727 (experimental)"


-- 

ramana at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dberlin at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-07-27 15:05:21
               date|                            |


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


  parent reply	other threads:[~2009-07-27 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17  6:56 [Bug target/40783] New: " carrot at google dot com
2009-07-17  6:56 ` [Bug target/40783] " carrot at google dot com
2009-07-27 15:05 ` ramana at gcc dot gnu dot org [this message]
2009-12-12  1:17 ` rearnsha at gcc dot gnu dot org
     [not found] <bug-40783-4@http.gcc.gnu.org/bugzilla/>
2021-07-26  8:07 ` pinskia 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=20090727150521.723.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).