From: Andrew MacLeod <amacleod@redhat.com>
To: Jeffrey Yasskin <jyasskin@google.com>
Cc: Lawrence Crowl <crowl@google.com>,
Benjamin Kosnik <bkoz@redhat.com>,
Richard Henderson <rth@redhat.com>,
Aldy Hernandez <aldyh@redhat.com>, GCC <gcc@gcc.gnu.org>
Subject: Re: C++11 atomic library notes
Date: Wed, 05 Oct 2011 20:12:00 -0000 [thread overview]
Message-ID: <4E8C70D4.5030109@redhat.com> (raw)
In-Reply-To: <CANh-dXnzJcs_LmtWc1jmM8jo0JDhxzax4gm+8_iGAkne-gb0Jw@mail.gmail.com>
On 10/05/2011 10:44 AM, Jeffrey Yasskin wrote:
>
> Yes, that's what I'm suggesting. The rule for 'volatile' from the
> language is just that "Accesses to volatile objects are evaluated
> strictly according to the rules of the abstract machine." If the
> instruction-level implementation for a 16-byte atomic load is
> cmpxchg16b, then that's just how the abstract machine is implemented,
> and the rule says you have to do that consistently for volatile
> objects rather than sometimes optimizing it away. That's my argument
> anyway. If there's another standard you're following beyond "kernel
> people tend to ask for it," the situation may be trickier.
perfect, I like it.
Andrew
prev parent reply other threads:[~2011-10-05 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E862864.2010607@redhat.com>
2011-10-01 6:56 ` Marc Glisse
2011-10-01 23:12 ` Andrew MacLeod
2011-10-02 8:40 ` Marc Glisse
2011-10-02 13:56 ` Andrew MacLeod
2011-10-03 17:31 ` Richard Henderson
2011-10-03 17:54 ` Andrew MacLeod
2011-10-03 18:10 ` Richard Henderson
2011-10-03 19:52 ` Joseph S. Myers
2011-10-05 7:26 ` Jeffrey Yasskin
2011-10-05 18:58 ` Andrew MacLeod
2011-10-05 19:07 ` Jeffrey Yasskin
2011-10-05 20:12 ` Andrew MacLeod [this message]
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=4E8C70D4.5030109@redhat.com \
--to=amacleod@redhat.com \
--cc=aldyh@redhat.com \
--cc=bkoz@redhat.com \
--cc=crowl@google.com \
--cc=gcc@gcc.gnu.org \
--cc=jyasskin@google.com \
--cc=rth@redhat.com \
/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).