This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: C++0x Memory model and gcc

From: Andrew MacLeod <amacleod at redhat dot com>
To: Miles Bader <miles at gnu dot org>
Cc: gcc at gcc dot gnu dot org
Date: Tue, 11 May 2010 08:49:03 -0400
Subject: Re: C++0x Memory model and gcc
References: <4BE5774B.3090709@bourguet.org> <4BE5C741.7070504@inria.fr> <mcrd3x4pdyc.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <4BE8411C.1030309@redhat.com> <buozl07hsdo.fsf@dhlpc061.dev.necel.com>

Miles Bader wrote:

Andrew MacLeod <amacleod@redhat.com> writes:
-fmemory-model=single - Enable all data races introductions, as they are today. (relax all 4 internal restrictions.)
One could still use this mode with a multi-threaded program as long as explicit synchronization is done, right?

Right. Its just a single processor memory model, so it doesn't limit any optimizations.

Andrew

Follow-Ups:
- Re: C++0x Memory model and gcc
  - From: Miles Bader

References:
- Re: C++0x Memory model and gcc
  - From: Jean-Marc Bourguet
- Re: C++0x Memory model and gcc
  - From: Albert Cohen
- Re: C++0x Memory model and gcc
  - From: Ian Lance Taylor
- Re: C++0x Memory model and gcc
  - From: Andrew MacLeod
- Re: C++0x Memory model and gcc
  - From: Miles Bader

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]