On Fri, May 5, 2017 at 12:30 PM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, May 5, 2017 at 11:44 AM, Matthias Kaehlcke <mka@xxxxxxxxxxxx> wrote: >> >> Indeed, I expect 4.12 (with this patch ...) to build with Clang for a >> x86 defconfig (with tons of warnings). ARM64 is very close. > > Does it actually *work*, rather than just build? > Yes, it does work. I have been using clang to build and run various 4.x based versions of Linux on both x86_64 and powerpc for over 6 months now. Assuming that you have a wrapper for clang that sets a few options and disables some warnings there really is very little else that is needed. powerpc currently only needs a single patch to the arch Makefile to add a cc-option check to a gcc specific flag. x86_64 needs the change that was under discussion here, but is still blocked by issues with building the 16 bit boot code. Supposedly this has now been fixed in clang, but I have not yet either seen or tried a version of the compiler with that fix. arm64 looks like it is also now very close. There are a few lingering places in the kernel which use variable length arrays in structs (eg the raid10 driver) which don't build with clang and that is about it. So, while I completely understand the resistance to adding arbitrary hacks to the kernel just to support another compiler it is important to also understand just how close things are to "just working". md -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|