Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754210AbaBQUSZ (ORCPT ); Mon, 17 Feb 2014 15:18:25 -0500 Received: from mail-ve0-f174.google.com ([209.85.128.174]:56725 "EHLO mail-ve0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752704AbaBQUSW (ORCPT ); Mon, 17 Feb 2014 15:18:22 -0500 MIME-Version: 1.0 In-Reply-To: <1392666947.18779.6838.camel@triegel.csb> References: <20140207180216.GP4250@linux.vnet.ibm.com> <1391992071.18779.99.camel@triegel.csb> <1392183564.18779.2187.camel@triegel.csb> <20140212180739.GB4250@linux.vnet.ibm.com> <20140213002355.GI4250@linux.vnet.ibm.com> <1392321837.18779.3249.camel@triegel.csb> <20140214020144.GO4250@linux.vnet.ibm.com> <1392352981.18779.3800.camel@triegel.csb> <20140214172920.GQ4250@linux.vnet.ibm.com> <1392486310.18779.6447.camel@triegel.csb> <1392666947.18779.6838.camel@triegel.csb> Date: Mon, 17 Feb 2014 12:18:21 -0800 X-Google-Sender-Auth: 3nI--o_Se4gNPjJN6C0VE6LanSo Message-ID: Subject: Re: [RFC][PATCH 0/5] arch: atomic rework From: Linus Torvalds To: Torvald Riegel Cc: Paul McKenney , Will Deacon , Peter Zijlstra , Ramana Radhakrishnan , David Howells , "linux-arch@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "akpm@linux-foundation.org" , "mingo@kernel.org" , "gcc@gcc.gnu.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 17, 2014 at 11:55 AM, Torvald Riegel wrote: > > Which example do you have in mind here? Haven't we resolved all the > debated examples, or did I miss any? Well, Paul seems to still think that the standard possibly allows speculative writes or possibly value speculation in ways that break the hardware-guaranteed orderings. And personally, I can't read standards paperwork. It is invariably written in some basically impossible-to-understand lawyeristic mode, and then it is read by people (compiler writers) that intentionally try to mis-use the words and do language-lawyering ("that depends on what the meaning of 'is' is"). The whole "lvalue vs rvalue expression vs 'what is a volatile access'" thing for C++ was/is a great example of that. So quite frankly, as a result I refuse to have anything to do with the process directly. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/