office hours: Wednesdays 2:00-3:00 pm (and by appointment) Levine 511
Teaching AssistantsOlek Gierczak
office hours: Tuesdays 12:00-1:30pm, GRW 5th Floor Bump Space
office hours: Tuesdays 6:00-7:00, GRW 6th Floor Bump Space
office hours: Monday 3:00-4:00pm, GRW 5th Floor Bump Space
office hours: Wednesday 6:00-7:00pm, GRW 565
Course information:  time: TR 3:00 - 4:30pm
room: David Rittenhouse Laboratory A2
Prerequisites: CIS 121 and CIS 240
- Code generation
- Semantic analysis
- 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
- Developing Applications with Objective Caml by Emmanuel Chailloux, Pascal Manoury and Bruno Pagano
- Introduction to Objective Caml by Jason Hickey
Projects: Building a Compiler
There are several homework projects. Homework 1 is an individual assignment. The rest of the projects are pair-programming projects -- students are strongly encouraged to work in pairs, but may ask permission to work alone on them.
CIS 341 Toolchain - instructions for getting access to the tools you need to complete course assignments.
- Homework 1: Hellocaml
Due: Wednesday, January 24th at 11:59pm
- Homework 2: X86lite
Due: Wednesday, February 7th at 11:59pm
- Homework 3: Compiling LLVMlite
Due: Monday, February 26th at 11:59pm
- Homework 4: Compiling Oat v.1
(Tentatively) Due: Wednesday, March 28th at 11:59pm
- Homework 5: Full Oat
(Tentatively) Due: Wednesday, April 11 at 11:59pm
- Homework 6: Dataflow Analysis and Register Allocation
(Tentatively) Due: Wednesday, April 25 at 11:59pm
- 12% Midterm - Date: Thursday, March 1 in class Midterm (2018) and Solutions (2018)
- Midterm (2017) and Solutions (2017)
- Midterm (2015) and Solutions (2015)
- Midterm (2013) and (partial) Solutions (2013)
- 18% Final exam - Date: TBA Solutions (2017)
- 70% Course 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.
General Project Guidelines
Teams for group projects will consist of one or two students.
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.
- Projects submitted late, but within 24 hours of the deadline are subject to a 15 point penalty.
- Projects submitted late, but between 24 and 48 hours of the deadline are subject to a 30 point penalty.
- If, for some reason, you have an extension of less than 48 hours on the homework, the extension only overrides the associated late penalty -- it does not extend the late period!
- 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.
- 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.
Academic IntegrityThis course will abide by the University's Code of Academic Integrity. In particular, for individual projects and group projects, the following guidelines should be followed:
- For individual projects, you must type in and edit
your own code, documentation, and any other materials submitted
- 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
- "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
Name: Chris Brown Email: ***@seas.upenn.edu I received tips from Jo Johnson on the i/o and example.com/mem.htm on memory ...
- "High level" discussions are fine.
- If there is any doubt about the use of external sources or collaboration, please ask for clarification by the course staff.