166 books
—
480 voters
Goodreads helps you keep track of books you want to read.
Start by marking “Engineering a Compiler” as Want to Read:
Engineering a Compiler
by
The proliferation of processors, environments, and constraints on systems has cast compiler technology into a wider variety of settings, changing the compiler and compiler writer's role. No longer is execution speed the sole criterion for judging compiled code. Today, code might be judged on how small it is, how much power it consumes, how well it compresses, or how many p
...more
Hardcover, 801 pages
Published
October 27th 2003
by Morgan Kaufmann Publishers
(first published September 2003)
Friend Reviews
To see what your friends thought of this book,
please sign up.
Reader Q&A
To ask other readers questions about
Engineering a Compiler,
please sign up.
Be the first to ask a question about Engineering a Compiler
Community Reviews
Showing 1-30

Start your review of Engineering a Compiler

Nov 11, 2019
Will Semin
added it
The book is full of valuable insights and good, elbaorate explanations. Well worth the read.

I hate to say this, but I wasn't as impressed with this book as I thought I should have been, GIVEN its place in the pantheon of programming books.
However, I still list this as a must read for all developers. ...more
However, I still list this as a must read for all developers. ...more

Jan 05, 2017
Andrew Obrigewitsch
rated it
it was amazing
·
review of another edition
Shelves:
computer,
educational
Given that this can easily be made into a very confusing and convoluted subject, this book does a really good job of simplifying Compiler Engineering. Still I must give a warning that this subject is not for the faint of heart.

Engineering a Compiler is an excellent introductory text on compilers. I particularly enjoyed the textbook's clean layout and design and cleanly written algorithms placed very close to the paragraphs where they are relevant.
Particularly after reading Muchnick, I found the amount of text explanation with a lack of concrete examples to be disturbing. Whole sections pass without any accompanying code examples. While I didn't think that pseudocode would have particularly enriched these topics, and I ...more
Particularly after reading Muchnick, I found the amount of text explanation with a lack of concrete examples to be disturbing. Whole sections pass without any accompanying code examples. While I didn't think that pseudocode would have particularly enriched these topics, and I ...more

It may be a great introduction, but I will never know. The problems with books like this is that they skim over topics not going deep into the subject ever. This book has some good chapters. The content in the book is not dense, it’s written in very dry academic style. In plain english, it is just boring. I cannot see anyone reading this book from cover to cover. And yet it is not a reference. I do not recommend it.

Alright book if you are looking for a good overview of compiler concepts. I read this while using the Dragon Book as a reference, and I think in the future I will definitely use the Dragon book to look up information, but this book did a much better job of explaining concepts in a non-technical way first.

GT Barnes & Noble 2009-01-0x. I've been reading too many books and papers about compilers the past few months to really enjoy this book very much, especially compared to Kennedy's and Muchinek's. This is kind of the "West End" or perhaps "Goals 2000" of the trio they form, with the least rigorous presentation and most minimal coverage. I think we're using this in CS6241 only because so many MS students are gormless waste-wits, admitted only to collect some tuition (I'm coming to loathe introduci
...more
There are no discussion topics on this book yet.
Be the first to start one »
Goodreads is hiring!
News & Interviews
Readers have a lot to look forward to this year! Just feast your eyes upon all of these debut books to check out and emerging authors to...
103 likes · 34 comments
No trivia or quizzes yet. Add some now »