public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/3506: weird behaviour when incrementing volatile ints Date: Wed, 03 Apr 2002 02:56:00 -0000 [thread overview] Message-ID: <20020403105602.17783.qmail@sources.redhat.com> (raw) The following reply was made to PR target/3506; it has been noted by GNATS. From: Richard Henderson <rth@redhat.com> To: Herbert Xu <herbert@gondor.apana.org.au> Cc: rth@gcc.gnu.org, 89949-quiet@bugs.debian.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: target/3506: weird behaviour when incrementing volatile ints Date: Wed, 3 Apr 2002 02:47:18 -0800 On Wed, Apr 03, 2002 at 08:29:27PM +1000, Herbert Xu wrote: > This breaks C99 wrt sig_atomic_t. The increment has to be a single > instruction. Um, no, *assignment* has to be a single instruction. Very different. r~
next reply other threads:[~2002-04-03 10:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-03 2:56 Richard Henderson [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-03 2:36 Herbert Xu 2002-03-29 2:42 rth 2001-07-01 9:06 Matthias Klose
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=20020403105602.17783.qmail@sources.redhat.com \ --to=rth@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).