Living with and Leveraging GCC
summary
GCC now officially accepts the effort to add COBOL frontend with the goal of a free compiler that runs legacy mainframe code without rewriting it, using flex and bison to parse a 1,280 page ISO COBOL and emitting GCC’s GENERIC trees, with custom HTML/JSON dump tooling and a proposal for a Lisp dump language to make internals testable. The implementation passes the NIST 1985 test suite, hits most of ISO 2023 features, is four years in, and still needs performance and completeness work.
AI-written summary · about
chapters (10)
- 0:00Introduction to GCC
- 3:54GCC as a multi-language compiler
- 7:06Adding Cobalt to GCC
- 12:04Challenges of GCC internals
- 17:15Documentation gaps in GCC
- 20:10Proposing Lisp for GCC internals
- 25:02Need for GCC documentation funding
- 31:05Documentation process for GCC
- 36:01Awkward implementation bugs
- 42:25Future of GCC and Cobalt
related talks
25mCrossover: Towards Compiler-enabled COBOL-C Interoperability
27mRust GCC Front-end
16mSoftware Language Engineers’ Worst Nightmare
01h 16m“What Has My Compiler Done for Me Lately? Unbolting the Compiler's Lid”
26mGCC BPF and Linux kernel
01h 04mCompiler Bugs And Bug Compilers
19mGCC Compiler Code Size Density
28mrustc_codegen_gcc: A gcc codegen for the Rust compiler