GCC Internals

Twelve lessons are written and the rest are not. The lessons lists what exists, with a Colab badge on each one, and the glossary is the one place every term in them is defined.

The films is the shortest way in if you would rather watch than read. Six of them, a minute or so each, each one showing the part of the pipeline that only makes sense as a sequence.

The blueprints are the other half of the project and are not lessons. A blueprint says what GCC does precisely enough to implement against, with every claim citing a line of the pinned source. Nine of a planned fifty eight exist, one of them finished. Read a lesson to understand something, read a blueprint to build it.

The plan is in the milestones, and what could still change it is in the open questions.

One more page is worth a look. Can a browser compile C here is a live Python notebook sitting in the middle of a documentation page, and pressing the button on it sends your C to a real GCC 16 and shows you the GIMPLE that comes back. Every hands on part of every lesson is going to work that way, so it is the first thing that had to be proved.