CS 444/644 - Compiler Construction (Winter 2015)


Tuesdays and Thursdays, 4:00 -- 5:20 PHY 235
Brad Lushman (bmlushma), DC 3110, Office hours: e-mail for appointment
Teaching Assistants:
Adriel Dean-Hall, Adam Roegiest (cs444@student.cs)
Web page:
Handbook description:
Final Exam:
Course Description and Objectives:
The objective of the course is to provide a thorough understanding of the basic structure of compilers for Java-like languages. A major part of the course consists of the implementation of a compiler for a simplified Java-like language. The goal of the course is to acquaint students with software tools and techniques which are applicable both to compilers and the implementation of system utility routines, command interpreters, etc.
Topics covered:
scanning, parsing, abstract syntax trees, scoping and name resolution, type checking, static analysis, runtime organization, code generation.
Acknowledgement: The Joos-related parts of the course are adapted by permission from Michael Schwartzbach's dOvs course at the University of Aarhus.

Web Resources

Recommended References


CS 444

Course Project: 75%
- online Marmoset tests: 60%
- written reports: 15%
Final Exam: 25%
You must achieve 50% or more on final exam in order to pass the course. If you do not meet this minimum requirement then your final grade for the course will be at most your final exam mark.

CS 644

Above CS 444 Marking Scheme, scaled: 80%
Literature Survey: 20%

Course Project

The overall project for the course is to write a compiler from Joos 1W, a fairly large subset of Java, to i386 assembly language (the Netwide Assembler dialect). The project will be done in groups of three. The project will be broken up into several assignments with fixed due dates. The assignments must be submitted to the Marmoset on-line submission and testing system. For each assignment, you will submit both your code and a written report (for assignments 1, 4, and 5) to Marmoset. Marks for your code will be reported to you by Marmoset, and your marked written reports will be returned to you by e-mail. The above assignment marks total 50% of your final mark. An additional 10% will be assigned to secret tests which will be run after the assignment 5 deadline.

Students enrolled in CS 644 are required to complete a literature survey on a topic related to compiler construction.

Resources available in the linux.student.cs environment.

Group Work Marking Policy

When working in a group, disagreements sometimes arise. One of the objectives of this course is for you to resolve such disagreements with sufficient, constructive, and frank communication within the group. Therefore, when disagreements arise, discuss them within the group before asking the instructor to intervene. If the group fails to reach a resolution, the group as a whole should arrange a meeting with the instructor. The instructor's role is primarily to mediate the discussion within the group, rather than to intervene in the disagreement.

Problems are easier to resolve if handled early. When a problem arises, try to resolve it as soon as possible. Do not leave it until the end of the course.

At the end of the course, the following policies will be used to distribute marks among the group members:

  1. Normally, each member of the group will be given an equal mark. You should therefore strive to ensure that each group member makes an approximately equal contribution to the project.
  2. The group may propose a different distribution of the marks, provided all group members consent to the distribution. Such a proposal must be made to the instructor within three days after the due date of the last assignment. The marks will be distributed in such a way that the mean of the marks equals the original group mark and no individual project mark exceeds 100%.
  3. If agreement cannot be reached, a member of the group must contact the instructor within three days of the due date of the last assignment. The instructor will ask each group member to submit a written statement detailing the contributions of each group member, the nature of the conflict, and the steps that were taken by the group to resolve the conflict. Failure to submit the statement within three days of being asked to do so will result in a mark of zero for that group member. Based on the statements, the instructor will make a final decision about the mark distribution. Note that the instructor will generally not deviate from the equal distribution of marks unless convinced that the group took sufficient and timely steps to resolve the conflict internally.

Late Policy

The written report for each assignment must be submitted by the assignment deadline. Reports submitted after the deadline will not be marked and will receive a mark of zero. If you cannot finish an assignment by the deadline, submit what you have by the deadline, and explain any unfinished parts in your report.

For code submissions, the following late policy is in effect: (0.5 * best-on-time) + (0.5 * best-overall), where

Examples: Submitting an additional solution for an assignment can never reduce your mark.

Academic Integrity Policies

[an error occurred while processing this directive]