From: Thomas Gleixner <tglx@linutronix.de>
To: Qian Cai <cai@lca.pw>, Marco Elver <elver@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Will Deacon <will@kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] READ_ONCE, WRITE_ONCE, kcsan: Perform checks in __*_ONCE variants
Date: Wed, 20 May 2020 00:05:08 +0200 [thread overview]
Message-ID: <87y2pn60ob.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAG=TAF7zVCMLj5US0uw-piwBUSmWpmPSPV3Thjbh7_kGsO88hQ@mail.gmail.com>
Qian Cai <cai@lca.pw> writes:
> On Tue, May 19, 2020 at 5:26 PM Marco Elver <elver@google.com> 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
next prev parent reply other threads:[~2020-05-19 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 18:38 Marco Elver
2020-05-12 19:09 ` Peter Zijlstra
2020-05-19 21:10 ` Qian Cai
2020-05-19 21:25 ` Marco Elver
2020-05-19 21:45 ` Qian Cai
2020-05-19 22:05 ` Thomas Gleixner [this message]
2020-05-20 2:28 ` Qian Cai
2020-05-20 2:47 ` Nathan Chancellor
2020-05-20 3:16 ` Qian Cai
2020-05-20 3:44 ` Nathan Chancellor
2020-05-20 7:28 ` Marco Elver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2pn60ob.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=cai@lca.pw \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®