In-memory and Persistent Representations of C++
summary
Claim: concrete, compiler-neutral in-memory and on-disk representations exist and are usable today. Implementation: an open IPR library under MIT captures a minimal, expression-based in-memory model; a binary IFC format is open on GitHub stores partitions, string tables, 32-bit typed references and a header with checksum. Results: MSVC emits IFCs, they’re roughly 10× smaller than PCHs, load back into compilers, and enable tooling (bindings, JIT). Status: spec and code need cross-compiler adapters and community contributions.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:45What is the next step
- 9:15Inmemory Representation
- 17:55Persistent Representation
- 18:30Compiler Principles
- 19:25Abstract away from concrete syntax
- 20:55Persistent data
- 22:25Generic programming
- 24:20Iterators
- 24:47Abstract Form
- 25:14Blob of Data
- 26:58Universal Algebra
- 28:26Modules Interface
- 29:01Semantic Data
- 31:34Why modules
- 32:32Copyright
- 33:08IoC
- 38:06FC File
- 40:02Header
- 43:57Abstract Reference
- 44:57Declarations
- 47:23Where do we go from here
- 50:39Summary
- 56:19Story
- 57:43Templates
related talks
30mInteractive C++ Compilation (REPL) Done in a Tiny and Embeddable Way
16mIRHash: Efficient Multi-Language Compiler Caching by IR-Level Hashing
53mDebug C++ Without Running
01h 00mDebug C++ Without Running
58mC++ Under the Hood: Internal Class Mechanisms
01h 04mProgramming with C++ Modules: Guide for the Working
50mSharing Is Caring - How to Let the Compiler Know What You're Thinking
52mThe Virtual Filesystem This Changes Everything
