Any and all information about 6.035 Fall 2019!
There are two websites for 6.035 fa19:
WE WILL MAKE ALL ANNOUNCEMENTS VIA PIAZZA, SO MAKE SURE THAT YOU ENROLL
If neither site has the information you need, you should email the TA's directly
2019
September October November December
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
1 2 3 4 5 6 7 1 2 3 4 5 1 2 1 2 3 4 5 6 7
8 9 10 11 12 13 14 6 7 8 9 10 11 12 3 4 5 6 7 8 9 8 9 10 11 12 13 14
15 16 17 18 19 20 21 13 14 15 16 17 18 19 10 11 12 13 14 15 16 15 16 17 18 19 20 21
22 23 24 25 26 27 28 20 21 22 23 24 25 26 17 18 19 20 21 22 23 22 23 24 25 26 27 28
29 30 27 28 29 30 31 24 25 26 27 28 29 30 29 30 31
Note: L: parsing~55
means that the topic was parsing
and we covered up to slide 55
- Professor
- Martin Rinard rinard@csail.mit.edu
- TA's
- Jackie Bredenberg jamb@mit.edu
- Jack Choi jchoi5me@mit.edu
- Prereq --
6.004
,6.031
- Level --
U
- Units --
4-4-4
Analyzes issues associated with the implementation of higher-level programming languages. Fundamental concepts, functions, and structures of compilers. The interaction of theory and practice. Using tools in building software. Includes a multi-person project on compiler design and implementation.
6.035 has no officially required textbook. All of the material you need is taught in class, with the exception of the documentation for your implementation language and associated libraries. However, the following books may be helpful in implementing various components of your compiler, and are available from MIT libraries.
Modern Compiler Implementation in Java (Tiger Book)
Andrew W. Appel and Jens Palsberg
Cambridge University Press, 2002
Many other resources such as technical papers, interesting and useful blog posts, and reference guides are available on the references page.
We will distribute assignments and make all announcements via Piazza and GitHub (this) page. Important announcements will also be made via email.
Since lecture dates are not all finalized at the start of the semester, please pay attention to the schedule.
Your grade in 6.035 is based upon four components: your compiler, two quizzes, and the mini-quizzes at the beginning of every lecture. You must therefore attend all lectures in order to take the mini-quizzes and receive a full grade.
For more information on the way the compiler project is graded, see the projects overview handout from the first recitation.
We expect you to attend all quizzes and submit the project on time. For extensions under extenuating circumstances (e.g., you are sick for a week, family emergencies), we require a letter from one of the student deans at S^3.
Although you may discuss the projects with anybody, you must develop the code yourself. For the scanner/parser project, you must develop your code alone. On all subsequent projects, you should work with your team members, but you may not develop or share any code with other teams.
You may collaborate on the mini-quizzes, but you may not collaborate with anybody on the full quizzes; doing so will result in a failing grade.
Do not post your lab or homework solutions on publicly accessible web sites or file spaces; this enables cheating for students in future years.
We will use the software provided by the Athena infrastructure to evaluate each group project. The project skeletons contain the scripts that will automatically build and run your projects.
The submitted project should be self-contained. With the exception of the languages and libraries provided by the Athena infrastructure, all code and libraries (when applicable; see the next section) should be contained within the submitted archive.
Make sure to build and run your compiler on the Athena infrastructure before submitting it for evaluation. If we are not able to automatically build or run your compiler using the scripts provided with the project skeletons, it will incur a 25% penalty on the number of points for this project.
In 6.035, you build a compiler almost entirely from scratch. There are a few allowed exceptions: you may use one of the approved parser generators, described in the first project & athena handouts. You may use various language APIs for working with collections and data types. However, there are some restrictions on that. For example, users of Haskell may not use Haskell's Data.Graph or Compiler packages.
Any libraries beyond the Java API or basic Scala libraries must be approved by the TA. We will not allow more advanced libraries, such as the PackratParsers package. In general, if you are unsure of whether or not you are allowed to use a piece of software, ask the TA.
Lectures:
- 11am-12pm MTWRF in 32-144.
To find out whether there is lecture on a given day, check calendar above.
For all general questions and/or concerns, please post on Piazza.
If the matter is private, please email the TA's directly.
Office Hours:
- Tuesday's 4pm-6pm in 34-304
- additional ones available via request
Relecture:
- Monday's 7pm-9pm in 34-304
- Thursday's 4pm-5pm in 34-304
- additional ones available via request
Note that relectures are only held if students email the TA's in advance to request one.
We will have additional office hours before each quiz and each phase of the project.
This section contains a number of useful and/or interesting references selected by the staff. You are not expected to know most of the material on this page for quizzes or for implementing your compiler; however, you may find it interesting and helpful.
- Decaf language spec TODO link
- The complete Intel x64 manual
- Intel x64 Optimization Reference Manual
- x64 wiki
- x64 cheat sheet -- lists and tables detailing registers and assembly commands
- x86-64 architecture guide -- a walkthrough with an example, and common commands
- Intel x64 manual
- Intel developer manual -- detailed description of some assembly instructions
- x64 cheat sheet -- lists and tables detailing registers and assembly commands
Interesting blog posts, papers, etc
- Overviews
- Blogs
- Russ Cox's Blog -- Russ is one of the developers of Google Go, a pretty interesting language.
- Ian Wienand's Blog -- Whoever he is, he writes about compiler and language internals, the magic black box that is the linker, and more
- Matt Might's Blog -- Matt is a professor at the University of Utah and has written some very interesting articles (e.g. "Yacc is dead")
- Papers
- Register Allocation & Spilling via Graph Coloring -- G.J. Chaitin / 1982. Great (short) paper on simple register allocation.
- Linear Scan Register Allocation
- Iterated Register Coalescing -- Lal George / 1996. Presents improvements/alternative to Chaitin's design. If Chaitin-style (+/-Briggs) register allocation isn't enough for you, this paper is a good read - actually, it's a good read anyway, to understand the tradeoffs
- Superword Level Parallelism combined with loop unrolling, a simple way to implement a vectorizing compiler
- Miscellaneous
- Scala Patterns for Compiler Design
6.823 Advanced Computer Architecture
lecture notes