Google compiles the Pixel 2 kernel with Clang. They shipped the device on Android 8.0 with a kernel compiled with Clang 4.0 (build.config commit and prebuilt kernel commit) and upgraded to Android 8.1 with a kernel compiled with Clang 5.0 (build.config commit and prebuilt kernel commit).
Google uses Clang's link-time optimization and control flow integrity in the Pixel 3 kernel, hardening it against return oriented programming attacks (LTO commit, CFI commit).
Google started compiling all Chromebook 4.4 kernels with Clang in R67 (commit, LKML) and going forward, Clang is the default compiler for all future versions of the kernel (commit).
Further information including videos of talks on the motive behind compiling with Clang can be found in the ClangBuiltLinux wiki.
TL;DR: Helps find bugs, easier for Google since all of AOSP is compiled with Clang, compiler specific features such as link-time optimization, and better static analysis for higher code quality.
msm-4.14 and newer uses clang by default so there is no need for a patch stack.
NOTE: I am not going to write this for beginnings. I assume if you are smart enough to pick some commits, you are smart enough to know how to run git clone
and know the paths of your system.
make O=out ARCH=arm64 <defconfig>
PATH="<path to clang folder>/bin:<path to gcc folder>/bin:${PATH}" \
make -j$(nproc --all) O=out \
ARCH=arm64 \
CC=clang \
CLANG_TRIPLE=aarch64-linux-gnu- \
CROSS_COMPILE=aarch64-linux-android-
After compiling, you can verify the toolchain used by opening out/include/generated/compile.h
and looking at the LINUX_COMPILER
option.
A couple of notes:
CLANG_TRIPLE
is only needed when using AOSP's version of Clangexport CC=clang
does not work. You need to pass CC=clang
to make
like above.BoardConfig.mk
file in your device tree: TARGET_KERNEL_CLANG_COMPILE := true
To test and verify everything is working:
m kernel
or m bootimage
out/target/product/*/obj/KERNEL_OBJ/include/generated/compile.h
file and look at the LINUX_COMPILER
option.The core Clang patchset comes from mainline. It has been backported to three places:
If your kernel has 4.4.165 or 4.9.139 and newer, you automatically have the patchset and can start building with Clang!
The branches in this repository will be dedicated to adding this patchset when it does not exist and enhancing it by fixing all of the warnings from Clang (from mainline, the Pixel 2 and 3, msm-4.9/msm-4.14, and my own knowledge).
msm-3.18-oreo - based on kernel.lnx.3.18.r33-rel. Uses msm-perf_defconfig
.
msm-3.18-pie - based on kernel.lnx.3.18.r34-rel. Uses msm-perf_defconfig
.
msm-3.18-android-10 - based on kernel.lnx.3.18.r41-rel. All relevant configs should build with -Werror
.
msm-4.4-oreo - based on kernel.lnx.4.4.r27-rel. Uses msmcortex-perf_defconfig
.
msm-4.4-pie - based on kernel.lnx.4.4.r35-rel. Uses msmcortex-perf_defconfig
.
msm-4.4-android-10 - based on kernel.lnx.4.4.r38-rel. All relevant configs should build with -Werror
.
msm-4.9-oreo - based on the latest Oreo branch for the Snapdragon 845 kernel.lnx.4.9.r7-rel. Uses sdm845-perf_defconfig
.
msm-4.9-pie - based on the latest Oreo branch for the Snapdragon 845 kernel.lnx.4.9.r11-rel. Uses sdm845-perf_defconfig
.
msm-4.9-android-10 - based on kernel.lnx.4.9.r25-rel. All relevant configs should build with -Werror
.
The general structure of these commits is as follows:
You should pick the commits that I have committed (nathanchance).
Additionally, there are fixes for:
Every time there is a branch update upstream, the branch will be rebased, there is no stable history here! Ideally, I will not need to add any commits but I will do my best to keep everything in the same order.
NOTE: 3.18 Clang is not supported officially by an OEM. I've merely added it here as I decided to support it with my Pixel XL kernel.
You can either use a prebuilt version of Clang (like from AOSP) or build a version yourself from the upstream sources.
For prebuilts, I recommend AOSP's Clang, which is used for both the kernel and the platform so it is highly tested. You can git clone
that repo to always have access to the latest version available, which is what I recommend. That is currently Clang 9.0.8. If you would like to just download the minimum version of Clang supported for the branches in this repo, direct tarball links are provided below:
If you would like to build the latest version of Clang, you can do so with tc-build
. There are a lot of fixes for the Linux kernel that happen in LLVM/Clang so staying up to date is critical. If you experience any issues with Clang and an Android kernel, please report them to this repo.
binutils are used for assembling (and usually linking) the Linux kernel right now. When using AOSP Clang, you should use AOSP's GCC to avoid weird incompatibility issues. If you want source-built binutils, there is a build-binutils.py
script available in tc-build
The preferred method for getting help is either opening an issue on this repository or joining the Linux kernel newbies chat on Telegram.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。