aboutsummaryrefslogtreecommitdiff
path: root/scripts/jobserver-exec
diff options
context:
space:
mode:
authorGravatar Nathan Chancellor <natechancellor@gmail.com> 2021-01-13 17:34:47 -0700
committerGravatar Masahiro Yamada <masahiroy@kernel.org> 2021-01-30 06:06:35 +0900
commited4e9e615b7ec4992a4eba1643e62ec2d9d979db (patch)
treedc002a395cf05f42449e1fd93ce09a2b09a90597 /scripts/jobserver-exec
parentRevert "checkpatch: add check for keyword 'boolean' in Kconfig definitions" (diff)
downloadlinux-ed4e9e615b7ec4992a4eba1643e62ec2d9d979db.tar.gz
linux-ed4e9e615b7ec4992a4eba1643e62ec2d9d979db.tar.bz2
linux-ed4e9e615b7ec4992a4eba1643e62ec2d9d979db.zip
Documentation/llvm: Add a section about supported architectures
The most common question around building the Linux kernel with clang is "does it work?" and the answer has always been "it depends on your architecture, configuration, and LLVM version" with no hard answers for users wanting to experiment. LLVM support has significantly improved over the past couple of years, resulting in more architectures and configurations supported, and continuous integration has made it easier to see what works and what does not. Add a section that goes over what architectures are supported in the current kernel version, how they should be built (with just clang or the LLVM utilities as well), and the level of support they receive. This will make it easier for people to try out building their kernel with LLVM and reporting issues that come about from it. Suggested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com> Reviewed-by: Nick Desaulniers <ndesaulnier@google.com> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'scripts/jobserver-exec')
0 files changed, 0 insertions, 0 deletions