public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mrd at alkemio dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/3506] weird behaviour when incrementing volatile ints Date: Tue, 17 May 2005 00:33:00 -0000 [thread overview] Message-ID: <20050517003305.5590.qmail@sourceware.org> (raw) In-Reply-To: <20010701090600.3506.89949-quiet@bugs.debian.org> ------- Additional Comments From mrd at alkemio dot org 2005-05-17 00:33 ------- (In reply to comment #8) > Did you read comment #1. Yes, but it's not clear. > GCC doesn't know what constitutes a reference to a volatile memory Is this to say the GCC developers believe the C language's definition of "volatile" is ambiguous, or that there are situations where "incl x" is operationally distinct from "movl x, %eax; incl %eax; movl %eax, x" when x is volatile? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3506
next prev parent reply other threads:[~2005-05-17 0:33 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20010701090600.3506.89949-quiet@bugs.debian.org> 2005-05-15 13:33 ` pinskia at gcc dot gnu dot org 2005-05-15 13:34 ` pinskia at gcc dot gnu dot org 2005-05-15 13:34 ` pinskia at gcc dot gnu dot org 2005-05-16 22:34 ` mrd at alkemio dot org 2005-05-16 22:57 ` pinskia at gcc dot gnu dot org 2005-05-17 0:33 ` mrd at alkemio dot org [this message] [not found] <bug-3506-4828@http.gcc.gnu.org/bugzilla/> 2007-08-18 0:06 ` pinskia at gcc dot gnu dot org 2007-08-18 0:13 ` pinskia at gcc dot gnu dot org 2008-12-28 2:49 ` pinskia at gcc dot gnu dot org [not found] <bug-3506-4@http.gcc.gnu.org/bugzilla/> 2020-07-27 2:06 ` pinskia at gcc dot gnu.org 2023-02-09 18:11 ` 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=20050517003305.5590.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: linkBe 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).