Topics:

• Lexing/Parsing
• Code generation
• Semantic analysis
• Optimization
• Run-time support

Reading and References

The following books contain useful course material, and much of the lecture content is derived from them (and other sources).

• Compilers (2nd edition) by Aho, Lam, Sethi, and Ullman
• Advanced Compiler Design and Implementation by Muchnick
• Modern Compiler Implementation in ML by Appel

• Real World OCaml
• OCaml Programming Style Guide
• The Caml Web Site, particularly the documentation and users' manual and the standard libraries
• OCaml.org
• Developing Applications with Objective Caml by Emmanuel Chailloux, Pascal Manoury and Bruno Pagano
• Introduction to Objective Caml by Jason Hickey

• Homework 1: Hellocaml
  Due: Thursday, January 22 at 11:59pm


• Homework 2: X86lite
  Due: Monday, February 2 at 11:59pm


• Homework 3: Compiling LLVMlite
  Due: Monday, February 23 at 11:59pm


• Homework 4: Compiling Oat v.1
  Due: Thursday, March 26th at 11:59pm


• Homework 5: Full Oat - Classes and Objects
  Due: Monday, April 6th at 11:59pm


• Homework 6: Dataflow Analysis and Optimizations
  Due: Monday, April 20th at 11:59pm


• Homework 7: Optimization and Experiments
  Due: Wednesday, April 29th at 11:59pm

Grading Criteria

• 12%   Midterm - Date: March 5th , in class.
• Midterm (2015) and Solutions (2015)
• Midterm (2008) and (partial) Solutions (2008)
• Midterm (2011) and (partial) Solutions (2011)
• Midterm (2013) and (partial) Solutions (2013)
• 16%   Final exam - Date: TBA
  • Final Exam (2008) and (partial) solution
  • Final Exam (2013) and (partial) solution
• 72%   Course projects (group projects)

Lecture Slides and Notes

Many of the slides in these lectures have been adapted (with permission) from course materials by Andrew Myers at Cornell University and Greg Morrisett at Harvard University.

Course Policies

General Project Guidelines

• Groups:
  Teams for group projects will consist of one or two students.
• Difficulty:
  The course projects are challenging and time consuming. They may require significant effort to understand the implementation details and concepts:
  Start Early!
• Late Projects:
  All projects are due at 11:59pm on the due date.
  • Each student has four late days to use as you wish throughout the semester. Each late day allows your group to submit an assignment up to 24 hours late. Late days are designed to accommodate unusual circumstances, such as short illness, travel, an unusually busy week, religous holidays, and other issues that crop up. Use them wisely.
  • You may use at most two late days on any given assignment. After two days, you will receive no credit.
  • Deadlines are automatically enforced. Forty-eight (48) hours after the deadline, the submission link will disappear. If you have fewer than two late days remaining, the like will disappear sooner.
  • Late days are deducted automatically. You do not need to ask permission to use them.
  • If you submit anytime after the deadline, you will use at least one late day. You cannot get your late day back, even if the version that you submitted before the deadline is your highest-scoring autograded version.
  If you have an extremely unusual circumstance, such as a serious and extended illness, contact the course instructor for special consideration.
• Regrade Policy:
  Regrade requests should be sent to the TA. Only reasonable requests will be considered. The entire project or exam will be regraded. Note that this means that the score on a regraded project might decrease.

Submission Policy

• Projects that do not compile will get no credit.
• Projects that compile will receive partial credit according to the grading guidelines provided in the project description.
• It is fine to submit a project multiple times. Only the last project submitted will count for grading purposes.

Academic Integrity

• For individual projects, you must type in and edit your own code, documentation, and any other materials submitted for grading.
  • Copying someone else's file is not allowed.
  • Allowing someone else to copy a file of yours, either explicitly or implicitly by leaving your code unprotected, is not allowed.
  • Editing each other's files is not allowed
• Regarding the ethics of what you may or may not discuss with others:
  • "High level" discussions are fine.
    For example, discussions about the problem statement.
  • "Low level" discussions are fine.
    For example, discussions about OCaml syntax or using omake, understanding compiler error messages, understanding the mechanics of the tools and libraries used for the projects.
  • "Mid level" discussions require discretion. In this CIS course, discussions at this level must be limited.  Unless explicitly stated otherwise, you may not collaborate significantly with classmates (except group project members) at this level.  If you have minor discussions with others at this level or get help from outside resources (tutors, web sites, etc), you must cite in the readme of the submitted projects the names of the people or websites who helped you and how they did. For example:

     Name: Chris Brown
     Email: ***@seas.upenn.edu
     I received tips from Jo Johnson on the i/o and example.com/mem.htm on memory
     ...

• If there is any doubt about the use of external sources or collaboration, please ask for clarification by the course staff.