4 ms·
Isn't that the other way around? I thought clang was trying to support all gcc extensions to be able to build Linux kernel. I would rather see both of these co
by belgesel 5y ago
Isn't that the other way around? I thought clang was trying to support all gcc extensions to be able to build Linux kernel.
I would rather see both of these compilers to stay competitive to push themselves higher.
- pjmlp 5y agoclang already builds Linux kernel on Mountain View dungeons, and it has been doing that for a couple of years now. Those changes just don't get to upstream.
- rincebrain 5y agoThat's...not true? https://www.kernel.org/doc/html/latest/kbuild/llvm.html https://www.kernel.org/doc/html/latest/kbuild/llvm.html I could be missing something, but I don't see any suggestion that you need a specific forked tree with patches to build with LLVM, and I've seen people filing bugs about using LLVM sanitizers to build the vanilla tree, so I don't think the expectation is that you need to apply a huge out of tree patchset for this to work any more?
- pjmlp 5y agoI follow Android, not Linux itself. My latest update was that not all patches were accepted upstream, or Google didn't care about upstreaming them, whatever. There are some Linux Plumbers talks, or from Linaro, about this a years back.
- yyyk 5y agoThere's an semi-official github[0] for this. AFAICT from the issues page, Clang and binutils/LLVM tools work fine with no patches for the mainstream archs and when not trying to be super-fancy with custom flags. The more non-mainstream one goes with arch or flags the more likely one will run into something. [0] https://github.com/ClangBuiltLinux/linux/issues https://github.com/ClangBuiltLinux/linux/issues (Note they use github for issues/wiki, not code, so no surprise the 'linux version' in code is oldish).
- jabl 5y agoKind of both. They've added some gcc-specific extensions to clang, but also removed some gcc-ism's from the Linux kernel.