Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I taught in the past and still like the trilogy of books

> Modern Compiler Implementation by Andrew W. Appel

It comes in three flavors C, ML (Meta Language), and Java

https://www.cs.princeton.edu/~appel/modern/

Writing a compiler in Standard ML is as natural as writing a grammar and denotational semantics.

Compiler writing is becoming an extinct art.



The ML version is my favourite and I can vouch for the books being quite interesting.

For more modern folks, one can use the ML version as inspiration for doing the book exercises in OCaml, Haskell, F# or Rust.

Writing compilers for a living, and CS research is a niche domain, not something I would consider an extinct art.


Thanks!

Are you sure it’s an extinct art though? LLVM is flourishing, many interesting IRs come to life like MLIR, many ML-adjacent projects build their own compilers (PyTorch, Mojo, tinygrad), many big tech like Intel, AMD, Nvidia, Apple and others contribute to multiple different compilers, projects integrate one to another at different levels of abstraction (PyTorch -> Triton -> CUDA) - there is a lot of compilation going on from one language to another

Not to mention many languages in a mainstream that weren’t that popular 10 years ago - think Rust, Zig, Go


The prominence of LLVM is a symptom of the dying of compiler writing as an art, not evidence of its vitality.


> compiler writing as an art

cooking is an art. software is engineering. no one would say "building skyscrapers as an art is dying".


You should look into GraalVM as well, as it is another approach for compiler development.


I'll take the bait.

Do you distinguish between writing a compiler and writing an optimizing compiler, and if so, how is writing an optimizing compiler an extinct art?

Equality saturation, domination graphs, chordal register allocation, hardware-software codesign, etc there are many new avenues of research for compilers, and these are just the ones on the top of my head that are relevant to my work. Most optimization work is R&D and much of it is left unimplemented at scale, and things like the phase-ordering problem and IR validation are hard to do in practice, even given ample resources and time.


I heard that the ML version was a translation of the C version, and is thus not easy to follow along. Or it may have been the other way around!


The other way around, the best book is the ML version, the other two try to do ML in the respective language.

Ironically, now with modern Java you can that much easier than the approach done in the Java variant back in 1997.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: