Re: [PATCH] READ_ONCE, WRITE_ONCE, kcsan: Perform checks in __*_ONCE variants

[Qian Cai]

> On May 19, 2020, at 6:05 PM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
> 
> 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.

Yes, it all make sense from that angle. On the other hand, I want to be focus on kernel rather than compilers by using a stable and rocket-solid version. Not mentioned the time lost by compiling and properly manage my own toolchain in an automated environment, using such new version of compilers means that I have to inevitably deal with compiler bugs occasionally. Anyway, it is just some other more bugs I have to deal with, and I donât have a better solution to offer right now.