Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!snorkelwacker!spdcc!esegue!compilers-sender From: markh@squirrel.labs.tek.com (Mark Henderson) Newsgroups: comp.compilers Subject: Re: Compiler Design in C How about it? Keywords: books, summary Message-ID: <1990Jun4.044858.15066@esegue.segue.boston.ma.us> Date: 4 Jun 90 04:48:58 GMT References: <1990Jun1.194941.5781@esegue.segue.boston.ma.us> Sender: compilers-sender@esegue.segue.boston.ma.us Reply-To: Mark Henderson Organization: Computer Research Laboratory, Tektronix, Inc., Beaverton OR Lines: 36 Approved: compilers@esegue.segue.boston.ma.us In article <1990Jun1.194941.5781@esegue.segue.boston.ma.us> Preston Briggs writes: >[quoting Holub, using unsafe optimizations is an OK idea] Fact is, historically the optimizer is where compiler writers have hung themselves. I've used several commercial compilers for which I often had to turn off the optimization to get them to handle some pretty mundane code properly. (I suppose there is no need to mention company names here). Part of the problem is that there is little (unified) theory of optimization and a lot of ad hoc techniques. Certainly the front end has a more complete. theoretical base. I guess the argument is, "that part is the easiest", but then consider that this is a textbook. I think the level of detail Holub is using to describe the front end will be useful to people learning about the front end. I don't think the intention of the book was to be an encyclopaedia of compiler design, either. The material seems more than adequate for a first course in compiler design. Optimization techniques could easily be a course or book in themselves. The book is already over 900 pages long... So what I'm saying is that I like the book, on the whole. Personally, I find the level of detail of code listings a bit aversive, but then they can always be skipped and referred back to for details. The explanations are clear. The diagrams are excellent. I really like the fact that lots of examples are given. Mark -- Mark Henderson, Tektronix, Inc., MS 50-662, P.O. Box 500, Beaverton, OR 97077 Telephone: +1 503 627 6280 FAX: +1 503 627 5502 TELEX: 6503784996MCI UW INTERNET: markh@squirrel.labs.tek.com ATTmail: !mchenderson MCI MAIL: 378-4996 X.400: ADMD=MCI/C=US/Surname=Henderson/Given_Name=Mark/DDA ID=3784996 -- Send compilers articles to compilers@esegue.segue.boston.ma.us {spdcc | ima | lotus}!esegue. Meta-mail to compilers-request@esegue. Please send responses to the author of the message, not the poster.