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). Copies of these books are on reserve in the Penn Engineering Library.

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

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

• Project 0: Hellocaml
  Due: Tuesday, January 22 at 11:59pm
  


• Project 1: X86lite
  Due: Thursday, January 31 at 11:59pm
  


• Project 2: Parsing and Compiling Expressions
  Due: Tuesday, February 12 at 11:59pm


• Project 3: Control Flow
  Due: Monday, February 25 at 11:59pm


• Project 4: Procedures and Arrays
  Due: Thursday, March 21 at 11:59pm


• Project 5: Objects and Inheritance
  Due: Monday, April 8 at 11:59pm


• Project 6: Optimizations
  Due:Thursday, April 18 at 11:59pm


• Project 7: Fun with OAT programming
  Due: Sunday, May 5 at 11:59pm

Grading Criteria

• 12%   Midterm - Date: 28 Feb. 2013, in class. SOLUTIONS
  • Example Midterm (2008) and (partial) Solutions (2008)
  • Example Midterm (2011) and (partial) Solutions (2011)
• 16%   Final exam - Date: Tuesday, April 30th noon-2:00pm
  • Example Final Exam Example Final Exam with Solutions
• 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. Late projects will be penalized as follows: projects up to two days late will receive a penalty of 10% of the total score, projects later than that will receive no credit.

  Students with legitimate excuses (illness, family emergencies, etc.) can request an extension. Please try to let the course staff know as soon as you are aware that your project might be late.

• 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.
• All projects should include a team.txt file that includes the following information:

  Team Members:
    pennkey	name		email
  
  
  Known issues with your implementation:
  
  
  
  ------------------------
  Course Project Feedback:
  ------------------------
  
  1.  How much time did it take to complete this project?
  
  
  2. How effective was this project? [0-10]: 
  
      0 = learned nothing
     10 = highly educational
  
  3. How engaging was this project? [0-10]:
  
      0 = tedious and boring
     10 = fun and engaging
  
  4. How difficult was this project? [0-10]:
  
      0 = piece of cake
     10 = extremely hard
  
     (note that hard is not necessarily bad, 
      if it's "hard" as in "challenging")
  
  [Feel free to add comments about this project]
  

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.