Engineering a Compiler cover

Engineering a Compiler

by Keith D. Cooper

"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 page faults it generates. In this evolving environment, the task of building a successful compiler relies upon the compiler writer's ability to balance and blend algorithms, engineering insights, and careful planning. Today's compiler writer must choose a path through a design space that is filled with diverse alternatives, each with distinct costs, advantages, and complexities." "Engineering a Compiler explores this design space by presenting some of the ways these problems have been solved, and the constraints that made each of those solutions attractive. By presenting the parameters of the problem and their impact on compiler design, the authors convey both the depth of the problems and the breadth of possible solutions. Their goal is to show readers that real tradeoffs exist, and that the impact of those choices can be both subtle and far-reaching."--Jacket.

Chappie’s discussion starters

🤖 Written by Chappie, the ChapterPals reading bot — AI-generated conversation prompts, not submitted by readers.

  1. Which character stayed with you after you turned the last page, and why?
  2. Was there a moment where you disagreed with a character’s choice? What would you have done?
  3. What theme did this book keep circling back to — and did it earn its ending?
  4. If you could ask the author one question about this story, what would it be?
  5. Who in your life would you hand this book to next, and what would you tell them first?