From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15106 invoked by alias); 7 May 2010 13:55:14 -0000 Received: (qmail 15098 invoked by uid 22791); 7 May 2010 13:55:14 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_FAIL X-Spam-Check-By: sourceware.org Received: from mx20.gnu.org (HELO mx20.gnu.org) (199.232.41.8) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 07 May 2010 13:55:10 +0000 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1OAO1E-0007dN-ID for gcc@gcc.gnu.org; Fri, 07 May 2010 09:55:08 -0400 Received: (qmail 19636 invoked from network); 7 May 2010 13:55:06 -0000 Received: from unknown (HELO ?192.168.0.104?) (mitchell@127.0.0.2) by mail.codesourcery.com with ESMTPA; 7 May 2010 13:55:06 -0000 Message-ID: <4BE41BBE.6020003@codesourcery.com> Date: Fri, 07 May 2010 13:55:00 -0000 From: Mark Mitchell User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Ian Lance Taylor CC: Andrew MacLeod , GCC Subject: Re: C++0x Memory model and gcc References: <4BE2E39A.5060706@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-operating-system: by mx20.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-05/txt/msg00129.txt.bz2 Ian Lance Taylor wrote: > -fmemory-model=single > Assume single threaded execution, which also means no signal > handlers. > -fmemory-model=fast > The user is responsible for all synchronization. Accessing > the same memory words from different threads may break > unpredictably. > -fmemory-model=safe > The compiler will do its best to protect you. That makes sense to me. I think that's an appropriately user-oriented view of the choices. -- Mark Mitchell CodeSourcery mark@codesourcery.com (650) 331-3385 x713