From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3800 invoked by alias); 4 Apr 2011 12:56:36 -0000 Received: (qmail 3772 invoked by uid 22791); 4 Apr 2011 12:56:36 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 04 Apr 2011 12:56:02 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p34Cu10D004033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 4 Apr 2011 08:56:01 -0400 Received: from houston.quesejoda.com (vpn-230-183.phx2.redhat.com [10.3.230.183]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p34Cu0s4032041; Mon, 4 Apr 2011 08:56:00 -0400 Message-ID: <4D99BFE0.30407@redhat.com> Date: Mon, 04 Apr 2011 12:56:00 -0000 From: Aldy Hernandez User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.9 MIME-Version: 1.0 To: Richard Guenther CC: Richard Henderson , Jeff Law , gcc-patches , Jakub Jelinek Subject: Re: [cxx-mem-model] bitfield tests References: <4D92103E.90100@redhat.com> <4D933A2E.9030105@redhat.com> <4D949416.5000307@redhat.com> <4D95FC41.5060003@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-04/txt/msg00208.txt.bz2 > But well, I guess the thing I don't like about the standard is that it makes > people that have started to be somewhat aware about threading issues > _less_ aware of them by providing some "false" safety to them. It > really smells like a standard designed for a very high-level language > where people don't have to think instead of a standard suitable for a > C family language. Well, that's not exactly true. You still need to think about threading. All the standard is doing is guaranteeing that if you already have a data race free program, the compiler won't add additional races not already there. But I'm not a C++ guy. I am no advocate for the standard. I'm just implementing stuff. Ahem, I'm just a soldier in this war :). Aldy