Mind the Gap (Between Your Code and Your Toolchain)

on YouTube ↗16m

" summary

Linkers hit a ~2 GB default limit for huge debug info and the practical fix is to emit split debug symbols (.dwo) which shrinks the binary to about 10–15% overhead while keeping full debuggability. Reproducible caching comes from mirroring sources to a deterministic path, an environment description (Docker/CMake toolchain) and a two-layer cache: L1/L2 content-addressable cache that lets builds share artifacts across machines. Profile builds with clang per-function timing or ninja tracing, and catch size regressions with Bloaty size profiler (delta analysis).

AI-written summary · about

" chapters (6)

1. 0:00Toolchain gaps
2. 1:11Debug symbols and linker limits
3. 4:38Build caching challenges
4. 8:57L1 and L2 caches
5. 11:08Profiling build process
6. 14:42Summary

" related talks

• 24m(Ab)using Compiler ToolsRéka Kovács · CppCon 2019
• 57mModern Linux C++ debugging tools - under the coversGreg Law · CppCon 2019
• 52mApplication-Level Debugging and Profiling: Gaps in the Tool EcosystemRosemary Francis · LinuxCon + CloudOpen Europe 2013
• 01h 04mCommon-sense acceleration of your MLOC buildMatt Hargett · CppCon 2014
• 01h 05mHow to Write a Heap Memory ProfilerMilian Wolff · CppCon 2019
• 01h 29mModern Linux C++ Debugging Tools - Under the CoversGreg Law, Dewang Li · ACCU 2021 Online
• 25mLLDB - a new C++ debuggerJan Kratochvíl · DevConf.CZ 2019
• 01h 00mLinkers, Loaders and Shared Libraries in Windows, Linux, and C++Ofek Shilon · CppCon 2023