Syllabus and general information for MCS-388: Compiler Design (Spring 2000)


MCS-388 attempts to draw together the theory and practice of compiler construction. Much of the material will have a strong theoretical foundation. However, with the exception of the last couple topics (due to time constraints), this material will serve as the basis for compiler-writing projects. Topics include lexical and syntactic analysis, naive code generation, data-flow analysis, register allocation and assignment, suppression of partial redundancies, and instruction scheduling.

Office hours

I will be available in my office (OHS 303) on Tuesdays from 10:30 to 11:20, on Wednesdays from 11:30 to 12:20, on Thursdays from 1:30 to 2:20 (except March 9), on Fridays from 2:30 to 3:20 (except March 10), and by appointment. You may send me electronic mail at or call me at extension 7466. I'll try to put any updates to my office hours on my web page, so check there if in doubt.

World Wide Web

All course materials will be available through my World Wide Web page. The URL for this course is After this syllabus I will give hardcopy handouts only to those students who want them.


MCS-388 draws heavily on MCS-265, MCS-287, and MCS-284. Some notions from MCS-375 and MCS-236 also crop up. You're expected to be able to program. Since the compiler-building tools and pre-existing code modules I supply will be centered around the Java programming language, the path of least resistance will probably be to learn that language as we go if you don't already know it. On the other hand, there are comparable compiler-building tools centered around other languages, so if you would rather use another language, that's fine too, you'll just have a little less of a support network. I'll gladly accept labs written in any programming language: C++, Scheme, ML, Ada, you name it.

Text and readings

Our primary text will be the ``red dragon book,'' i.e., Compilers: Principles Techniques and Tools by Alfred V. Aho, Ravi Sethi, and Jeffrey D. Ullman, Addison Wesley, 1986. We will also use some additional material: documentation, some of which will be on-line or in the lab area and some of which I'll hand out, and supplementary readings, which I will hand out. (There's also an on-line Java Tutorial at, hardcopies of that tutorial in the BookMark as a supplemental text for MCS-270, and copies of a couple Java books in the MCS Lab monitors' room, any of which you are welcome to use as a supplement.)


On Thursdays, we will meet in the OHS 326 computer lab rather than in the usual classroom. Each lab has two or three lab days set aside for us to work together, but will also require you to spend additional time out of class.

Attendance is mandatory for all lab sessions, unless you have already turned in your lab report. I will excuse up to three absences per student, for any reason. Use yours wisely. If you exceed this allowance, I may reduce your course grade by one letter grade.

As shown on the syllabus, the first week we will swap the activities for Thursday and Friday: class on Thursday 2/10, lab on Friday 2/11.


Students are encouraged to discuss the course, including issues raised by the assignments. However, the solutions to assignments should be individual original work unless otherwise specified. If an assignment makes you realize you don't understand the material, ask a fellow student a question designed to improve your understanding, not one designed to get the assignment done. To do otherwise is to cheat yourself out of understanding, as well as to be intolerably dishonorable.

Any substantive contribution to your solution by another person or taken from a publication should be properly acknowledged in writing. Failure to do so is plagiarism and will necessitate disciplinary action.

The same standards regarding plagiarism apply to team projects as to the work of individuals, except that the author is now the entire team rather than an individual. Anything taken from a source outside the team should be be properly cited.

One additional issue that arises from the team authorship of project reports is that all team members must stand behind all reports bearing their names. All team members have quality assurance responsibility for the entire project. If there is irreconcilable disagreement within the team it is necessary to indicate as much in the reports; this can be in the form of a ``minority opinion'' or ``dissenting opinion'' section where appropriate.

Late assignments

All assignments are due at the beginning of class on the day indicated. Late assignments will be penalized by one ``grade notch'' (such as A to A- or A- to B+) for each weekday late or fraction thereof. However, no late assignments will be accepted after graded assignments are handed back or solutions are distributed.

If you are too sick to complete an assignment on time, you will not be penalized. Simply write ``late due to illness'' at the top of the assignment, sign your name and hand it in. Other circumstances will be evaluated on a case-by-case basis.

Grade changes

Please point out any arithmetic or clerical error I make in grading, and I will gladly fix it. You may also request reconsideration if I have been especially unjust.


I will provide you with a letter grade on each homework assignment and lab assignment, in addition to the mid-term and final grades, so that you may keep track of your performance. As a guideline, the homeworks will contribute approximately half of your final grade, with the labs contributing the other half. However, I reserve the right to subjectively adjust your final grade. Please see me if you have any question how you stand. Class participation is not graded; however, it allows you to find and repair the gaps in your understanding before doing the assignments, and thus can dramatically improve your grade. You are responsible for all course material, whether or not you are present when it was covered or distributed.

Style guidelines

All assignments should be readily readable, and should not presuppose that I already know what you are trying to say. Use full English sentences where appropriate (namely almost everywhere) and clear diagrams, programs, etc. Remember that your goal is to communicate clearly, and that the appearance of these technical items plays a role in this communication process. Be sure your assignments are always stapled together and that your name is always on them.


Please contact me immediately if you have a learning or physical disability requiring accommodation.


In the reading column, section 0 means the material at the beginning of a chapter before the first section. When a reading is indicated as going to a particular page number, it means up to the heading on that page. The same section number on the next class day then indicates to finish the section.

This is my best guess as to the rate at which we will cover material. However, don't be shocked if I have to pass out one or more revised syllabi.
2/71.0-2.2Introduction, syntax definition
2/92.3-2.4Syntax-directed translation
2/102.5-2.6Your first compiler (a Thursday class)
2/11Lab 1: A First Compiler (a Friday lab)

2/143.0-3.1, 3.3, 3.5Lexical analysisHW 1
2/16Lexical-analyzer generators
2/17Lab 1 (continued)
2/184.0-4.2Context-free grammars

2/214.3Writing a grammarLab 1
2/234.4-p.188Top-down parsing
2/24Lab 2: Adding Variables
2/254.4More on predictive parsingHW 2

2/284.5, 4.7-p.220Bottom-up parsing
3/14.7-p.230SLR parser generation
3/2Lab 2 (continued)
3/34.7-p.240Canonical LR and LALR parser generation

3/64.8-p.251, 4.9Using ambiguous grammars; parser generatorsLab 2
3/85.0-5.3Syntax-directed definitions
3/9Lab 3: Generating Better Code from ASTs (sorry, no instructor)
3/10No class

3/135.4-5.6L-attributed definitions; bottom-up attribute evaluationHW 3
3/158.0-8.1Intermediate code
3/16Lab 3 (continued)
3/178.2-8.3, p.481Declarations and simple assignments

3/208.3Array access; type conversions
3/228.4Control flow
3/23Lab 3 (continued)
3/246.0-6.4Type checkingLab 3

4/37.0-7.2Run-time environments
4/57.3Storage-allocation strategies
4/6Lab 4: Control Flow and Scoping
4/7Modern run-time environment issuesHW 4

4/109.0-9.3Code generation
4/129.4Basic blocks and flow graphs
4/13Lab 4 (continued)
4/1410.0-10.2OptimizationLab 4

4/1710.4Loops in flow graphs
4/1910.5Data-flow analysis
4/20Lab 5: Procedures

4/2610.6Iterative data-flow analysis (11:30-12:00)
4/27Lab 5 (continued)
4/28More data-flow analysisHW 5

5/1Lab 5 (continued)
5/3notesLiveness analysis, interference graphs
5/4More on register allocation
5/5Yet more on register allocation

5/8Lab 6: Wildcard LabLab 5
5/10notesSuppression of partial redundancy
5/11Lab 6 (continued)
5/12notesInstruction schedulingHW 6

5/15More on instruction scheduling
5/17Synthesis; evaluationLab 6

Course web site:
Instructor: Max Hailperin <>