Building Linux with Clang/LLVM¶
This document covers how to build the Linux kernel with Clang and LLVM utilities.
The Linux kernel has always traditionally been compiled with GNU toolchains such as GCC and binutils. Ongoing work has allowed for Clang and LLVM utilities to be used as viable substitutes. Distributions such as Android, ChromeOS, and OpenMandriva use Clang built kernels. LLVM is a collection of toolchain components implemented in terms of C++ objects. Clang is a front-end to LLVM that supports C and the GNU C extensions required by the kernel, and is pronounced “klang,” not “see-lang.”
The compiler used can be swapped out via
CC= command line argument to
CC= should be set when selecting a config and during a build.
make CC=clang defconfig make CC=clang
A single Clang compiler binary will typically contain all supported backends, which can help simplify cross compiling.
make ARCH=arm64 CC=clang CROSS_COMPILE=aarch64-linux-gnu-
CROSS_COMPILE is not used to prefix the Clang compiler binary, instead
CROSS_COMPILE is used to set a command line flag:
clang --target=aarch64-linux-gnu foo.c
LLVM has substitutes for GNU binutils utilities. Kbuild supports
to enable them.
They can be enabled individually. The full list of the parameters:
make CC=clang LD=ld.lld AR=llvm-ar NM=llvm-nm STRIP=llvm-strip \ OBJCOPY=llvm-objcopy OBJDUMP=llvm-objdump READELF=llvm-readelf \ HOSTCC=clang HOSTCXX=clang++ HOSTAR=llvm-ar HOSTLD=ld.lld
The integrated assembler is enabled by default. You can pass
As explained above,
CROSS_COMPILE is used to set
CROSS_COMPILE is not specified, the
--target=<triple> is inferred
That means if you use only LLVM tools,
CROSS_COMPILE becomes unnecessary.
For example, to cross-compile the arm64 kernel:
make ARCH=arm64 LLVM=1
LLVM_IAS=0 is specified,
CROSS_COMPILE is also used to derive
--prefix=<path> to search for the GNU assembler and linker.
make ARCH=arm64 LLVM=1 LLVM_IAS=0 CROSS_COMPILE=aarch64-linux-gnu-
LLVM does not target all of the architectures that Linux supports and
just because a target is supported in LLVM does not mean that the kernel
will build or work without any issues. Below is a general summary of
architectures that currently work with
of support corresponds to “S” values in the MAINTAINERS files. If an
architecture is not present, it either means that LLVM does not target
it or there are known issues. Using the latest stable version of LLVM or
even the development tree will generally yield the best results.
defconfig is generally expected to work well,
certain configurations may have problems that have not been uncovered
yet. Bug reports are always welcome at the issue tracker below!
|Architecture||Level of support||