public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ivan at vmfacility dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/26933] Volatile member in struct member accessed/written implicitly
Date: Wed, 29 Mar 2006 21:18:00 -0000	[thread overview]
Message-ID: <20060329211815.391.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26933-5984@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from ivan at vmfacility dot fr  2006-03-29 21:18 -------
Created an attachment (id=11158)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11158&action=view)
Runnable program demonstrating the problem

This program, once compiled for powerpc64 and run on powerpc64 demonstrates a
volatile field being implicitly accessed/changed by the explicit change of a
neighbouring value.


-- 


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


  reply	other threads:[~2006-03-29 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 21:10 [Bug c/26933] New: " ivan at vmfacility dot fr
2006-03-29 21:18 ` ivan at vmfacility dot fr [this message]
2009-04-01  1:01 ` [Bug middle-end/26933] " bje at gcc dot gnu dot org
2009-04-09  6:17 ` bje 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=20060329211815.391.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).