This course focuses on the design and implementation of compilers. Topics covered include the structure of one-pass and multiple-pass compilers; symbol table management; lexical analysis; traditional and automated parsing techniques; syntax-directed translation and semantic analysis; run-time storage management; intermediate code generation; introduction to optimization; and code generation. This course requires a substantial, semester-long programming project implementing a functional compiler that includes lexical and syntactic analyzers, a type checker, and a code generator.
We rely on one textbook:
Additionally, a reference on ML will be useful, such as the following:
Please join the Piazza site to post questions.
Each student is given 100 discretionary late hours for programming assignments, but any one assignment may only be up to 72 hours late (this is because we will post the sample solution after then). These are calendar hours, not business hours. As the homework assignments are submitted electronically, the "write date" on the student's homework file will be considered the completion date for late assignments.
After you use up all of your discretionary late hours, assignments turned in late will be graded according to the following formula: S = R * (1 - t / c), where S is the grade given, R is the grade the work would have gotten if turned in on time, t is the amount of time by which the work was late, and c is equal to four days. Thus, the value of a late assignment decays daily, with a half-life of just over two days. Examples: work turned in five minutes late gets 99.9% credit, one hour late gets 99.0% credit, six hours late gets 93.8% credit, one day late gets 75.0% credit, two days late gets 50.0%, and three days late gets 25.0%. Assignments submitted more than 72 hours late will not be accepted.
There will be no extensions due to scheduling conflicts, computer downtime, or other such factors, except under truly extraordinary circumstances. Extensions will be granted only for university-sanctioned excuses such as illness, and then only with the proper documentation. You are responsible for planning ahead and managing your time so that you can complete the assignments on time. You must either finish on time or accept the consequences of doing otherwise.
Please check your project group to see which assignment you should implement for the compiler back-end.
Please be sure to regularly check this page for updates.
To submit your solutions to the programming assignments electronically, first change to the directory where your solutions are, and then use the following command.
/c/cs421/bin/submit number filesnumber is the assignment number and files is the list of files for that assignment. For example,
/c/cs421/bin/submit 3 README sources.cm tiger.lexsubmits the files README, sources.cm, and tiger.lex for a fictitious assignment 3.
The submit command copies your files to the directory /c/cs421/SUBMIT/number/login and lists all the files that you have submitted for assignment number. Here, login is your user account name.
There is also unsubmit, which allows you to retract one or more files. For example,
/c/cs421/bin/unsubmit 3 tiger.lexwould remove your tiger.lex from the submission directory.
You can also check what files you have submitted by using the check command. For example,
/c/cs421/bin/check 3would list all the files your have submitted so far for assignment 3.
Usually, you can omit the /c/cs421/bin/ prefix if /c/cs421/bin/ is already added to your PATH variable.
The course website is based on
the design by Robert Grimm.
The course content is based on a
previous course by Zhong Shao.