Every time you compile C, C++, Rust, Swift, or run code through most ML frameworks, one person’s work is doing the heavy lifting underneath. You have never thought about it. That is the point.
Chris Lattner wrote LLVM as his master’s thesis at the University of Illinois. A compiler infrastructure project. The kind of thing that would normally be read by twelve people and forgotten.
Instead, it became the most widely used compiler backend in the world.
What LLVM actually does
When you write code in a programming language, something has to turn that code into instructions a processor can execute. That “something” is a compiler, and LLVM is the engine inside most of them.
Clang (the C/C++ compiler used by Apple, Google, and most of the industry) runs on LLVM. The Rust compiler uses LLVM. Swift, the language Lattner also created at Apple, compiles through LLVM. Julia uses LLVM. Dozens of other languages rely on it.
When NVIDIA compiles CUDA code for GPU execution, LLVM is involved. When you train an ML model and the framework optimizes the computational graph, LLVM-derived technology is often underneath.
It is everywhere. And it is invisible.
The pattern of one person
Lattner did not just build LLVM. He created Swift at Apple, giving iOS developers a modern language that replaced Objective-C. He created MLIR, the compiler framework that is now the backbone of ML compiler stacks at Google and beyond. He is now building Mojo, a language designed to be Python but fast, targeting AI workloads.
One person. Four foundational contributions. Each one would be a career-defining achievement on its own. Combined, they represent one of the most productive individual contributions to computing infrastructure in the last two decades.
Why “unsung” still applies
Developers in the compiler community know Lattner. He is a prominent figure in that world. But the broader tech world, the millions of developers who write code that LLVM compiles, has no idea. They type cargo build or swift build and it works. They do not think about why.
The infrastructure is invisible by design. Good compilers are like good plumbing: you only notice them when they break. LLVM almost never breaks.
What this says about impact
There is a category of contribution that is so foundational it disappears into the background. Nobody thanks the compiler when their code runs fast. Nobody credits the compiler backend when their language gets adopted.
Lattner built the machine that builds the machines. And then he built three more. And then he started a company to build a fifth.
The code you wrote today was probably compiled by his work. Tomorrow’s code probably will be too.