This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/52558] write introduction incorrect wrt the C++11 memory model
- From: "aldyh at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 12 Mar 2012 15:56:30 +0000
- Subject: [Bug c++/52558] write introduction incorrect wrt the C++11 memory model
- Auto-submitted: auto-generated
- References: <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.