public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52558] write introduction incorrect wrt the C++11 memory model
Date: Mon, 12 Mar 2012 15:56:00 -0000	[thread overview]
Message-ID: <bug-52558-4-W6IccwfytB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52558-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Aldy Hernandez <aldyh at redhat dot com> 2012-03-12 15:56:30 UTC ---
On 03/12/12 10:45, rguenther at suse dot de wrote:

>> Just to get this straight, am I to assume that the default code
>> generation for GCC is a single threaded environment?  I just want to
>> make sure I get these variants right in my head, and can properly
>> separate what is and is not allowed in default GCC, and what only
>> pertains to the C11 memory model (or transactional stuff).
>
> It certainly is, though we are getting more careful about this stuff
> in recent years and generally only read data-races are ok.
>
> Richard.
>

Ah, ok.  Now it's clear.  I was confused because in a previous thread 
months ago you had mentioned that read data-races were ok, but write 
data-races were not, whereas here we are even allowing write data races.

Understood.

Thanks.


  parent reply	other threads:[~2012-03-12 15:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 10:26 [Bug c++/52558] New: " francesco.zappa.nardelli at gmail dot com
2012-03-12 14:54 ` [Bug c++/52558] " aldyh at gcc dot gnu.org
2012-03-12 15:01 ` rguenth at gcc dot gnu.org
2012-03-12 15:25 ` amacleod at redhat dot com
2012-03-12 15:29 ` aldyh at gcc dot gnu.org
2012-03-12 15:33 ` rguenther at suse dot de
2012-03-12 15:43 ` aldyh at redhat dot com
2012-03-12 15:45 ` rguenther at suse dot de
2012-03-12 15:51 ` amacleod at redhat dot com
2012-03-12 15:56 ` aldyh at redhat dot com [this message]
2012-03-12 15:58 ` rguenther at suse dot de
2012-03-13  7:30 ` [Bug tree-optimization/52558] " francesco.zappa.nardelli at gmail dot com
2012-03-13 21:20 ` [Bug c++/52558] " torvald at gcc dot gnu.org
2012-03-28 19:08 ` [Bug tree-optimization/52558] " aldyh at gcc dot gnu.org
2012-04-10 17:08 ` aldyh at gcc dot gnu.org
2012-04-11  8:16 ` rguenth at gcc dot gnu.org
2012-04-11 13:37 ` aldyh at gcc dot gnu.org
2012-04-11 14:08 ` rguenther at suse dot de
2012-05-31 19:55 ` aldyh at gcc dot gnu.org
2012-05-31 20:07 ` aldyh at gcc dot gnu.org
2012-05-31 20:27 ` torvald at gcc dot gnu.org
2012-06-14 19:23 ` aldyh at gcc dot gnu.org
2012-06-14 21:15 ` aldyh at gcc dot gnu.org
2012-07-02 18:26 ` aldyh 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-52558-4-W6IccwfytB@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).