On Fri, Mar 17, 2017 at 7:03 PM, Borislav Petkov <bp@xxxxxxxxx> wrote: > On Fri, Mar 17, 2017 at 01:32:00PM +0100, Alexander Potapenko wrote: >> > IIUC there's only a handful of VLAIS instances in LLVM code, why not >> Sorry, "kernel code", not "LLVM code". >> > just drop them for the sake of better code portability? > > And what happens if someone else adds a variable thing like this > somewhere else, builds with gcc, everything's fine and patch gets > applied? Or something else llvm can't stomach. > > Does that mean there'll be the occasional, every-so-often whack-a-mole > patchset from someone, fixing the kernel build with llvm yet again? This problem is more general and is not specific to clang. It equally applies to different versions of gcc, different arches and different configs (namely, anything else than what a developer used for testing). A known, reasonably well working solution to this problem is a system of try bots that test patches before commit with different compilers/configs/archs. We already have such system in the form of 0-day bots. It would be useful to extend it with clang as soon as kernel builds. -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
