Department of Computer Science and Engineering
POSTECH

CSED 423: Compiler Design

Prof. Hanjun Kim

Fall 2015

General Information | Schedule and Readings | Assignments

Course Summary

Understand the design and construction of compilers. Concepts include syntactical analysis, semantics, code generation, optimization, and run-time systems. A complete compiler for a small language will be implemented in ML.


Announcements

2/20 - Welcome!

Administrative Information

Lectures: MW 11:00am-12:15pm, B2-107
Lab: W 6:30-7:45pm, PIRL-142
Professor: Hanjun Kim, hanjun@, C5 217, 279-8865
Office hours: MW after class or by appointment
Teaching Assistants:
Bongjun Kim, bong90@, C5 201 Compiler Research Lab.
Office hours: TBA
Seonyeong Heo, heosy@, C5 201 Compiler Research Lab.
Office hours: TBA

Required Texts:
Recommended Text:

Software

Install SML/NJ v.110.78 on your computer.

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.

Documentation:

Grading

Your grade will be calculated as follows:

Assignments

Weekly programming assignments, as listed in the last column of the schedule, are due Mondays at 11:00pm.

You can get help with the assignments at Lab, or by emailing to or visiting Professor Hanjun Kim or the teaching assistants. Ask for help when you need it!

Assignments should be turned in on time so the grader can grade everybody's assignments together and get the graded assigments back to you quickly. If you turn in the assignments late, you derail this process. We can forgive a couple of hours lateness, but after that we must impose penalties, 10%/day.

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.

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. Do not let anyone copy your program. Writing code for use by another or using another code in any form violates the University's academic regulations.