On Thu, Jul 11, 2019 at 02:18:08PM -0300, Jason Gunthorpe wrote: > On Thu, Jul 11, 2019 at 10:16:44AM -0700, Nick Desaulniers wrote: > > On Thu, Jul 11, 2019 at 6:39 AM Jason Gunthorpe <jgg@xxxxxxxx> wrote: > > > > > > On Thu, Jul 11, 2019 at 01:14:34AM -0700, Nathan Chancellor wrote: > > > > Maybe time to start plumbing Clang into your test flow until it can get > > > > intergrated with more CI setups? :) It can catch some pretty dodgy > > > > behavior that GCC doesn't: > > > > > > I keep asking how to use clang to build the kernel and last I was told > > > it still wasn't ready.. > > > > > > Is it ready now? Is there some flow that will compile with clang > > > warning free, on any arch? (at least the portion of the kernel I check) > > > > $ make CC=clang ... > > > > Let us know if you find something we haven't already. > > https://clangbuiltlinux.github.io/ > > https://github.com/ClangBuiltLinux/linux/issues > > What clang version? > > Jason You'll need clang-9 for x86 because of the asm-goto requirement (or a selective set of reverts for clang-8) but everything else should be good with clang-8: https://travis-ci.com/ClangBuiltLinux/continuous-integration/builds/118745131 We wrote a Python script that builds an LLVM 9 toolchain suitable for kernel development that is self contained (doesn't install anything to your system): https://github.com/ClangBuiltLinux/tc-build Let me know if there are any issues with it if you give it a go, I've already fixed one from Thomas Gleixner: https://lore.kernel.org/lkml/alpine.DEB.2.21.1906262140570.32342@xxxxxxxxxxxxxxxxxxxxxxx/ Cheers, Nathan
