Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp46235ybk; Tue, 19 May 2020 15:07:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJygbz4ut5VWQPYotWjLe+eNYWwjTHgSgloh+QEoVzwpqEVdBU6AlhRql5CSt31EQKTQWT47 X-Received: by 2002:a17:906:8694:: with SMTP id g20mr1252519ejx.75.1589926056682; Tue, 19 May 2020 15:07:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589926056; cv=none; d=google.com; s=arc-20160816; b=mIHI2TdnkD0sIu9hN5Wj9iwOZPq7aLpscKb2o5VEh6ztSW4AM6W15BElVVSDQreWGb dpOHNDlJ+ttl+iL3XhtTeDAOUlXPwWNCygD24MNdhoQirl7s4OW0ioYHd1sJqZKy8aIo Jl2TJqU+hW0gqP4maISvR6ejt6JKTtclefxbhQgSgusV3swFSOvdbH983VyX/PlCafqX 58y+5m02i0ygTkJKLO2yHJs4xTqyGZa4xXjZkol2ZI9ewKfT8QaSjt114gv9aLEauj2h dE/FO24CjFhWSjXiN8nGboKVcIrhpyKLkRdmTyXjMN1zbLb3NPZPP5/b/vPqAW1/qmix bfpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=gxgghm6Iry1BPo7TrfsrSuwaAd/7nlUWdom8Em+Qj/g=; b=uIKA1/NdzJVeWrRq8zGjUsLxDugAU4EB9Zg539RlcwJznWLlFSX7Y4VqS/ONIi+Hj/ d7lrL32MWrXo6YDh1HZOz4ev9CfK21sLSd50bkSrZ6Bq9HSx4X8LmHqX3UwMAadxAXqf fizzbBssEZ5NgSl8Vafl36eh6zvHWk5Wf/e7+YerRP2yKRg3Fysg5Yd9l/qX6pwIPjLr 7sTFsKN5XsBj1Fu5hJ3Ok9GqPNF0KOxIJX+yv+fVJINchtKgyw6ONhAe03nNEFP3ztfT CzbY5xSQ/38A/JNkLLfUH1X/+KYa9yviyjvdpuws+EZ+osjvRN0xIPbep0LVarY1PrMl JMIg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s16si367974edu.512.2020.05.19.15.07.13; Tue, 19 May 2020 15:07:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726489AbgESWFP (ORCPT + 99 others); Tue, 19 May 2020 18:05:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43728 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725885AbgESWFO (ORCPT ); Tue, 19 May 2020 18:05:14 -0400 Received: from Galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8F100C061A0F for ; Tue, 19 May 2020 15:05:14 -0700 (PDT) Received: from p5de0bf0b.dip0.t-ipconnect.de ([93.224.191.11] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1jbAMH-0003FU-EL; Wed, 20 May 2020 00:05:09 +0200 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id B6FD5100606; Wed, 20 May 2020 00:05:08 +0200 (CEST) From: Thomas Gleixner To: Qian Cai , Marco Elver Cc: Peter Zijlstra , Linux Kernel Mailing List , kasan-dev , Will Deacon , "Paul E . McKenney" , Ingo Molnar Subject: Re: [PATCH] READ_ONCE, WRITE_ONCE, kcsan: Perform checks in __*_ONCE variants In-Reply-To: References: <20200512183839.2373-1-elver@google.com> <20200512190910.GM2957@hirez.programming.kicks-ass.net> Date: Wed, 20 May 2020 00:05:08 +0200 Message-ID: <87y2pn60ob.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Qian Cai writes: > On Tue, May 19, 2020 at 5:26 PM Marco Elver wrote: >> The new solution is here: >> https://lkml.kernel.org/r/20200515150338.190344-1-elver@google.com >> While it's a little inconvenient that we'll require Clang 11 >> (currently available by building yourself from LLVM repo), but until >> we get GCC fixed (my patch there still pending :-/), this is probably >> the right solution going forward. If possible, please do test! > > That would be quite unfortunate. The version here is still gcc-8.3.1 > and clang-9.0.1 on RHEL 8.2 here. It will probably need many years to > be able to get the fixed compilers having versions that high. Sigh... > Also, I want to avoid compiling compilers on my own. Yes, it's unfortunate, but we have to stop making major concessions just because tools are not up to the task. We've done that way too much in the past and this particular problem clearly demonstrates that there are limits. Making brand new technology depend on sane tools is not asked too much. And yes, it's inconvenient, but all of us have to build tools every now and then to get our job done. It's not the end of the world. Building clang is trivial enough and pointing the make to the right compiler is not rocket science either. Thanks, tglx