public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/41849] optimization fails when register variables are used for an interrupt
Date: Wed, 20 Apr 2011 19:46:00 -0000	[thread overview]
Message-ID: <bug-41849-4-Z2theDxlb1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41849-4@http.gcc.gnu.org/bugzilla/>

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

Georg-Johann Lay <gjl at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gjl at gcc dot gnu.org,
                   |                            |hendrixgr at gmail dot com
          Component|rtl-optimization            |target
      Known to work|                            |4.5.0

--- Comment #1 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2011-04-20 19:45:54 UTC ---
Unfortunately, we don't see the exact command line.

I don't see this for 4.5.0, tried -O, -O2, -Os, -O3. All gives

foo:
/* prologue: function */
/* frame size = 0 */
/* stack size = 0 */
.L__stack_usage = 0
    sts timer0_h8_buf,r3
/* epilogue start */
    ret

Note that volatile on register variables does not work as expected. volatile is
meaningful for memory locations only.

As the addresses in your snipp indicate there is much more code in the module,
so presumably we don't see the proper source.


       reply	other threads:[~2011-04-20 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-41849-4@http.gcc.gnu.org/bugzilla/>
2011-04-20 19:46 ` gjl at gcc dot gnu.org [this message]
2011-07-25 15:19 ` gjl at gcc dot gnu.org
2011-07-25 15:22 ` gjl at gcc dot gnu.org
2011-07-25 15:26 ` gjl 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-41849-4-Z2theDxlb1@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).