public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "a dot kaiser at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/45052]  New: [4.5 regression] volatile ignored
Date: Sat, 24 Jul 2010 10:51:00 -0000	[thread overview]
Message-ID: <bug-45052-9820@http.gcc.gnu.org/bugzilla/> (raw)

"volatile" seems to have no effect. ReadByte should be called 4 times with
results merged in a word, instead it is called once and replicated 4 times.

arm-none-eabi-gcc -S -Os -mcpu=arm926ej-s src.c

-O0, -O2, -O3 are fine, -O1 and -Os are bad.


-- 
           Summary: [4.5 regression] volatile ignored
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: a dot kaiser at gmx dot net
  GCC host triplet: yagarto 01.05.2010
GCC target triplet: arm-none-eabi


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


             reply	other threads:[~2010-07-24 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24 10:51 a dot kaiser at gmx dot net [this message]
2010-07-24 10:52 ` [Bug c/45052] " a dot kaiser at gmx dot net
2010-07-24 10:54 ` a dot kaiser at gmx dot net
2010-07-24 11:44 ` a dot kaiser at gmx dot net
2010-07-24 14:37 ` [Bug tree-optimization/45052] [4.5/4.6 Regression] " rguenth at gcc dot gnu dot org
2010-07-26  9:27 ` rguenth at gcc dot gnu dot org
2010-07-31  9:35 ` [Bug tree-optimization/45052] [4.5 " rguenth at gcc dot gnu dot org
2010-07-31 12:13 ` rguenth at gcc dot gnu dot org
2010-07-31 12:13 ` rguenth 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=bug-45052-9820@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).