Marco Elver <el...@google.com> writes: > On Thu, 14 May 2020 at 17:09, Thomas Gleixner <t...@linutronix.de> wrote: >> >> Peter Zijlstra <pet...@infradead.org> writes: >> > On Thu, May 14, 2020 at 03:35:58PM +0200, Marco Elver wrote: >> >> Any preferences? >> > >> > I suppose DTRT, if we then write the Makefile rule like: >> > >> > KCSAN_SANITIZE := KCSAN_FUNCTION_ATTRIBUTES >> > >> > and set that to either 'y'/'n' depending on the compiler at hand >> > supporting enough magic to make it all work. >> > >> > I suppose all the sanitize stuff is most important for developers and >> > we tend to have the latest compiler versions anyway, right? >> >> Developers and CI/testing stuff. Yes we really should require a sane >> compiler instead of introducing boatloads of horrible workarounds all >> over the place which then break when the code changes slightly. > > In which case, let me prepare a series on top of -tip for switching at > least KCSAN to Clang 11. If that's what we'll need, I don't see a > better option right now.
And for a change that might make this time GCC people look at their open bugs. :) /me mumbles jumplabels and goes back to juggle patches
