Tag
build-systems
- Jan 17, 2026 Hermetic Build Actions: Enforcing That Compilation Reads Only Declared Inputs A declared input list is a promise. Making the promise enforceable means restricting the file system, the clock, and the network, and choosing which of those restrictions is worth its cost. compilers
- Sep 11, 2025 Build, Host, and Target: Three Machines in One Toolchain Why a cross build needs three machine names rather than two, which of them selects the compiler, and how a compiler that runs somewhere other than where it was built gets produced. systems programming
- Oct 17, 2024 Configure Tests That Execute Cannot Survive a Cross Build Run-time feature checks answer questions about whichever machine runs them, and caching makes the wrong answers outlive the build. Which tests can be converted, and which must be replaced by a declaration. systems programming
- Nov 15, 2023 Feedback Latency as Compounding Interest A slow test suite charges every change a fixed toll and inflates batch size, which makes each failure harder to diagnose. The queueing mechanics behind that second effect. software architecture
- Feb 15, 2023 Scheduling a Parallel Build from a Dependency Graph A build is a DAG of commands with known costs and unknown costs alike. Choosing what to run next determines both wall-clock time and how badly a late-discovered dependency hurts. compilers