AOSP Toolchains: Where we are with building kernels, bootloaders and AOSP with Clang
summary
AOSP userland already builds with Clang and efforts extend that toolchain to kernels, bootloaders and BSPs using two CI flows that build Clang master then prebuilt Clang images; resulting system images boot on HiKey/Lava boot tests and show about 0.1% size diff versus previous builds with occasional couple-percent performance gains. Replacing GNU ld with LLD increases size ~7–8% and exposes missing flags; mainline kernels mostly buildable (some modules and GCC plugins fail), U-Boot and some firmware still need work.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:43Building AOSP with Clang
- 7:23Transition to next speaker
- 10:48Building bootloaders with Clang
- 18:12Building Trusty and OctOS with Clang
- 20:43Q&A
related talks
46mYocto Project and Android – Compare and Contrast
38mBuilding Embedded Systems with AOSP - Why You Should Consider, Best Practices and...
14mAOSP Devboards
37mA Developer's Diary: The Trials and Triumphs of Maintaining Devboards in AOSP
38mHow to Enable Android (AOSP) on Your Developer Board
35mAOSP customization
38mHow to Enable Android (AOSP) on Your Developer Board
32mAndroid Open Source: What more can we do with Android?
