public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "regehr at cs dot utah.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/47409] New: volatile struct member bug
Date: Sat, 22 Jan 2011 04:13:00 -0000	[thread overview]
Message-ID: <bug-47409-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: volatile struct member bug
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: regehr@cs.utah.edu


The load/store shouldn't go away (especially at -O0).

regehr@home:~$ current-gcc -O0 vol.c -S -o - 
foo:
    pushl    %ebp
    movl    %esp, %ebp
    popl    %ebp
    ret

regehr@home:~$ cat small.c

const volatile int g_2 = 1;
int g_1 = 0;

void func_1 (void) {
   g_1 = g_2;
}

int main (void) {
  g_1 = g_2;
  return 0;
}

regehr@home:~$ current-gcc -v

Using built-in specs.
COLLECT_GCC=current-gcc
COLLECT_LTO_WRAPPER=/mnt/z/z/compiler-install/gcc-r169118-install/libexec/gcc/i686-pc-linux-gnu/4.6.0/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: ../configure --with-libelf=/usr/local --enable-lto
--prefix=/mnt/z/z/compiler-install/gcc-r169118-install
--program-prefix=r169118- --enable-languages=c,c++
Thread model: posix
gcc version 4.6.0 20110122 (experimental) (GCC)


             reply	other threads:[~2011-01-22  3:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22  4:13 regehr at cs dot utah.edu [this message]
2011-01-22  5:08 ` [Bug c/47409] " regehr at cs dot utah.edu
2011-01-24 16:47 ` jakub at gcc dot gnu.org
2011-01-24 16:53 ` regehr at cs dot utah.edu
2011-01-24 16:57 ` jakub at gcc dot gnu.org
2011-01-25  2:17 ` joseph at codesourcery dot com
2011-01-25 11:11 ` rguenth at gcc dot gnu.org
2011-01-25 16:24 ` regehr at cs dot utah.edu
2011-01-25 17:28 ` joseph at codesourcery dot com
2013-01-30  4:36 ` regehr at cs dot utah.edu
2013-01-30 11:39 ` rguenth at gcc dot gnu.org
2013-01-30 11:44 ` jakub at gcc dot gnu.org
2013-01-30 23:24 ` regehr at cs dot utah.edu
2013-02-06 11:47 ` jakub at gcc dot gnu.org
2013-02-06 15:00 ` jason at gcc dot gnu.org
2013-02-07  1:42 ` joseph at codesourcery dot com
2013-07-09  8:48 ` francesco.zappa.nardelli at gmail dot com
2013-09-13  9:38 ` rguenth at gcc dot gnu.org
2013-09-13  9:52 ` rguenth at gcc dot gnu.org
2013-09-13 10:38 ` francesco.zappa.nardelli at gmail dot com
2013-09-13 11:51 ` rguenth at gcc dot gnu.org
2013-09-13 14:46 ` francesco.zappa.nardelli at gmail dot com
2014-02-16 13:13 ` jackie.rosen at hushmail dot com
2021-08-05 23:52 ` pinskia at gcc dot gnu.org
2022-07-17 21:00 ` pinskia at gcc dot gnu.org
2024-01-18  6:02 ` 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=bug-47409-4@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).