public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64458] [ARM] Redundant ldr when accessing var inside and outside a loop
Date: Fri, 16 Jan 2015 14:29:00 -0000	[thread overview]
Message-ID: <bug-64458-4-4fqE4BJLY4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64458-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64458

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-01-16
                 CC|                            |ramana at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
Huh, what arch options ? 

    .arm
    .syntax divided
    .file    "ldr.c"
    .text
    .align    2
    .global    g
    .type    g, %function
g:
    @ Function supports interworking.
    @ args = 0, pretend = 0, frame = 0
    @ frame_needed = 0, uses_anonymous_args = 0
    @ link register save eliminated.
    ldr    r2, .L5
    ldr    r3, [r2]
.L2:
    cmp    r3, #0
    bne    .L2
    mov    r3, #1
    str    r3, [r2]
    bx    lr
.L6:
    .align    2
.L5:
    .word    glob
    .size    g, .-g
    .comm    glob,4,4


  reply	other threads:[~2015-01-16 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31 16:33 [Bug target/64458] New: " thopre01 at gcc dot gnu.org
2015-01-16 14:29 ` ramana at gcc dot gnu.org [this message]
2015-01-28  2:43 ` [Bug target/64458] " thopre01 at gcc dot gnu.org
2015-01-28  2:46 ` thopre01 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=bug-64458-4-4fqE4BJLY4@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).