Compact C Type Format in the GNU Toolchain
summary
Added CTF support lands across the GNU toolchain: GCC emits CTF, the linker performs fast type deduplication, binutils can dump and a GNU poke description edits encoded CTF, and GDB reads CTF; libabigail ingests CTF-only binaries for ABI checks. Output sizes shrink dramatically (example 3.2MB→200KB→60–70KB; Emacs 7MB→200KB→129KB). Work targets CTF V4 to add an async-friendly backtrace section (AMD64/AArch64 first) and a phased call-site scheme based on storage classes plus optional stack-saved arguments.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:47Welcome
- 2:26Debug Information
- 3:11Dwarf
- 5:30What is CDF
- 6:13CDF vs Dwarf
- 7:22CDF Dictionary
- 8:41CDF Types
- 9:35CDF Info
- 10:32Integer Data Type
- 12:03CRF Types
- 15:50Compression
- 16:43Toolchain support
- 17:45API support
- 18:23Demo
- 21:46Whats coming
- 22:46Online vs Offline Back Tracing
- 25:18Online Back Tracing
- 27:31Issues with EFrame Based Unwinders
- 29:16Unwind Formats
- 31:36CDF Frame
- 32:38Callsite Information
- 36:14Callsite Information Edition
- 37:11Summary
- 37:38CTF
- 38:14Wrapup
related talks
51mGraph-based ABI analysis for fun and profit
43mToolchains for the Future
23mAlways present type information thanks to BPF: BTF
31mToolchains for People in a Hurry: Latest Features of GCC/GLIBC
45mSupporting BPF in the GNU Toolchain
24m(Ab)using Compiler Tools
43mLiving with and Leveraging GCC
51mCompile-time tools supporting generic programming in C++