Riker: Always-Correct and Fast Incremental Builds from Simple Specifications
summary
Riker instruments builds with ptrace, seccomp/BPF and an injected library to record system calls into a new TraceIR that models the entire POSIX filesystem (files, directories, pipes, metadata and anti-dependencies). From a single command spec like "gcc .c" Riker auto-discovers and replays only changed commands, caches produced artifacts, and iterates until stable, achieving a median overhead 8.8% on full builds and 94% of make's incremental speedup* across 14 projects including LLVM and memcached.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:28How Riker Works
- 6:17Riker observes builds with system call tracing
- 7:40Problems with a Build Dependence Graph
- 16:46Performance
- 17:26Full Build Overhead
- 20:14Building Redis
- 21:52Incremental Builds
related talks
15mBuild Scripts with Perfect Dependencies
22mStay Ahead with the Latest Advances in RISC-V Development Tools
19mthe path to achieve a bug-free build on the mainline
28mImproving Build Time SBoMs
40mPanel: Toolchains & Runtime
38mStrategies to speed up build iteration, or dynamic hot reloading
23mtoolchain-agnostic build time improvements
11mRISC-V customization, HW/SW co-optimization, and custom compute