Princeton University
|
Computer Science 320
|
|
Understand the design and construction of compilers. Concepts include syntactical analysis, semantics, code generation, optimization, and run-time systems. Problems in processing imperative languages, such as C and Pascal, as well as functional languages such as ML, will be examined. A complete compiler for a small language will be implemented in ML.
This year, we will examine the multicore problem and JITs.
Prerequisites: 217 and 226.
The special project is an independent work alternative to the canned compiler project. Participation in this alternative is by special arrangement with Prof. August.
Install SML/NJ on your computer. We will be using SML/NJ version 110.67. Follow the instructions on this page. You may find it useful to run SML under emacs. This will let
you take advantage of rudimentary support for automatic
indentation, syntax-highlighting, and special keybindings.
Details.
Software
The final exam is worth twice as much as the midterm.
The late policy is to encourage submissions that are on-time. Any project can be late for up to 3 days without penalty. Up to 7 days total may be used during the semester, so use your late days wisely. After 3 days, zero credit is given for the assignment.
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.
Penalties are waived only for unforeseen circumstances, like illness, and then only with an appropriate written excuse.
Programming, like composition, is an individual creative process. Individuals must reach their own understanding of the problem and discover a path to its solution. During this time, discussions with friends are encouraged. However, when the time comes to write the code that solves the problem, such discussions are no longer appropriate - the program must be your own work (although you may ask teaching assistants for help in debugging). If you have a question about how to use some feature of C, UNIX, ML, etc., then you can certainly ask your friends or the teaching assistants.
Do not, under any circumstances, copy another person's program. Writing code for use by another or using another code in any form violates the University's academic regulations.