Compilation Course

Winter 2005-2006

Instructor:Mooly Sagiv
Assistant: Greta Yorsh

Links

• Compilation Course Forum
• Lecture Homepage

Grades

• The weight of each PA appears in the second row of the table.
  
• The grade of TA1 is a bonus to the final grade.
  

Important!! Verify that your grades (for all assignments) appear correctly in the list.

09/04/05: Submit your appeals (regarding any of the assignments) within a week from today.
Appeals submitted later will not be taken into consideration.

NEWS

• 09/04/06: PA5 and Bonus grades are now available.

• 23/03/06: Exam Grades
  
  • notebook - mispar mahberet behina.
  • id suffix - last 4 digits of your id, including sifrat bikoret.

• Devotedly working on PA5 in Purim :-)

• 15/03/06: Due to a popular demand, the submission deadline for PA5 is extended by 12 hours: submit PA5 by noon (12 be-tzohoraim), Thursday, 16/03/06.
• 05/03/06: For the Bonus assignment, if you use pipes (e.g., mycoolc script) to glue together different parts of the compiler, you might need to modify the correpsonding lexer/parser.
  Do not modify the auto-generated *.java files of the lexer/parser!
  Use the spec files for jflex and javaCup:
  [tokens.lex] [ast.lex] [ast.cup]
• 05/03/06: PA4 grades are now available.
  The total grade for PA4 is 0.4*good + 0.4*bad + 0.1*tests + 0.1*reame, where good is the grade for the good inputs computed by the automatic checker, bad is the grade for the bad inputs checked manuall, tests is the grade for the bad.cl and good.cl tests you submitted, and readme is the grade for README and the rest.
  Note that the log file which was sent to you automatically contains both good and bad inputs and outputs, but the grade for bad inputs was not taken into account, only the grade for good inputs.
  The checked README printouts of PA4 with comments are in my mail-box (Schrieber, 1-st floor, mailbox 260). Pick it up until 15/03/06.
  The grade on the README printout is the grade that appears in the column "Man": the sum of all manual grades, out of 60, i.e., 0.4*bad + 0.1*test + 0.1 * readme as above. The column "Auto" contains the grades of the autocheck for the good inputs, out of 100.
• 23/02/06: Sample Exam from last year's compilers class.
• 22/02/06: Extension: PA5 and the bonus assignment are both due 15/03/06.
  This is a firm deadline, no additional extensions will be given.
• 21/02/06: The exam is "open material", but you are not allowed to use a laptop for the exam.
• 04/02/06: Bonus assignment - one week extension. The extended deadline is 15/03/06.
• 31/01/06: New distribution of PA5 is now available. The distribution uses several packages and a simplified AST hierarchy.
  • To compile the new distribution and run it on example.cl, type in your working directory:
    gmake buildall
  • The auto-checker scropt is configured as follows:
    If the file cool-tree.java is found in your working directory, we assume you are using the original distribution (either PA5J.tar.gz or PA5JE.tar.gz), and copy the following files:

    CgenClassTable.java

    CgenNode.java

    CgenSupport.java

    StringSymbol.java

    IntSymbol.java

    BoolConst.java

    cool-tree.java

    TreeConstants.java

    Otherwise, the script will copy all *.java files in your working directory and its subdirectories, and compile and run it similarly to the target "buildall" in the Makefile of PA5JEP.tar.gz.
    Of course, example.cl and README are copied in both cases.
  • You are free to modify the existing definitions, and add new files and packages. Specify in the README which distribution you are using. If you are using the new distribution, list the new files/packages you use.
• 31/01/06: Bonus assignment is now available.
• 29/01/06: PA5 is now available. See notes below about CoolAid and additional documentation.
• CoolAid is installed at ~compiler/bin/ directory.
  • To use the GUI (graphic user interface) - only on Linux machines or via X-server connection (e.g., if you use Exceed to connect to nova), run the command:
    %> coolaid myfile.s
  • To use coolaid in a batch mode (for example, if you SSH to nova using TeraTerm), run the command:
    %>coolaid -batch myfile.s assuming that the directory ~compiler/COOL_DIR/bin/ is on your PATH.
  • The 'anngen' binary in ~compiler/COOL_DIR/bin/ directory is a phase of the reference compiler that emits the annotations needed by Coolaid (basically, a serialization of the class hierarchy). The script 'newcoolc' is a modification of 'mycoolc' script which calls the 'anngen' phase to append the annotations to the generated code, so that the result can be used with Coolaid.
  • We recommend you to run coolaid from ~compiler account on nova. Currently, source distribution is not available. To run Coolaid on your machine, you will need Tcl/Tk version >= 8.3 and glibc >= 2.3.2.
• Additional Documentation for PA5:
  • Cool Runtime System (with Coolaid additions): [PS] [PDF]
  • Coolaid Reference Manual: [PS] [PDF]
  • The theory behind Coolaid (not required for PA5): [PDF]

• 17/01/06: PA3 grades are now available.
• 11/01/05: One week extension for submitting PA4. PA4 due 25/01/06.
  The deadline for submitting PA5 postponed to one week after the exam in compilers. PA5 due 08/03/06.
  
• 27/12/05: Eclipse-friendly distribution PA4JE.tar.gz is now available.
• 15/12/05: PA3 - line numbers: If the only difference between the AST that your parser outputs and the AST of the reference parser is the line numbers, no points will be reduced in the autocheck (for correct inputs).
  However, differences in line numbers often indicate real problems in your parser. Make sure you you test your parser thoroughly.
• 10/12/05: PA2 grades are now available.
• 09/12/05: PA4 is already available.
• 07/12/05: Another update of Utilities.java: fixed the range of printable characters in printEscapedString method. This change will not affect the tests of your lexer implementations of PA2.
• 07/12/05: Update for questions 2ab in TA1

  Is there LR(0) parsing table for dl1 grammar ?
  If yes, construct it.
  If not, explain how to resolve the conflict based on one look-ahead: for every look-ahead token, which action is to be taken (shift or reduce).
  When resolving the conflicts, make sure that the language accepted by your conflict-free parser is the same as the language accepted by the original grammar.

• 05/12/05: Permanent change in time/classroom of 0368-3133-03 Tirgul session: starting from this Wednesday, 07/12/05, the session will take place

  on Wednesdays between 11:00-12:00, in Schreiber 006

  instead of Wednesdays between 12:00-13:00 in Schreiber 008.
• 05/12/05: New version of Utilities.java is now available. Fixed output format for STR_CONST and ERROR tokens (method printToken) matches the reference parser.
• 28/11/05: TA1 is now available.
• 28/11/05:
Dangling Else/If-Else Ambiguity
• 28/11/05: PA1 grades are now available for all project teams.
• PA2 - Do NOT use %line directive in your lexer specification.
• 13/11/05: There were inconsistencies in the sample.test and sample.out files in the original distribution of PA1.tar.gz. The file PA1.tar.gz available now is correct. The text of the assignment PA1.ps was originally correct.
• Please verify your details in the list of teams. Send me the missing details (marked with yellow).
• The subject of the Tirgul sessions on Nov. 09 is object-oriented programming and java tutorial.
• To print the slides properly, choose "Pure Black and White" option from the "Color/grayscale" combo-box in the "Print" menu.

Project Teams

Schedule

Presentations and Related Material

• If your POWER POINT does not show certain mathematical characters use these fonts. Make sure to extract to the appropriate directory, or install via the the Control Panel.

Time and Location

The Cool Project

• As part of the requirements in the Compilation course you will implement a Cool compiler (adapted with permission from Prof. Alex Aiken).
• The Classroom Object-Oriented Language Cool is a small language designed for use in an undergraduate compiler course project. While small enough for a one term project, Cool still has many of the features of modern programming languages, including objects, automatic memory management, and strong static typing.
• This project is adapted with permission from course material used in Berkeley and Stanford universities.

Project Guidelines

• The Cool compiler implemented in Java
• The project implements a complete compiler from Cool to MIPS
• Implementation process split into assignments
• The project is to be implemented in teams of 2 or 3 students.
• Your are required to split into teams during the first week of the semester.
• Your are required to submit all assignments within the same team.
• All team members will receive the same grade for the assignments.
• Each team member is required to fully understanding all the code, even parts she/he didn't directly work on.
• Different teams must not share code, but may share ideas
• Choose one of the member to be responsible for the "team account ": all assignments by this team should be submitted on her/his nova account.
• Important: send an email to me with the subject "Compilation - new project team", list of members (first name, last name, id, username on nova), and the team-account username (the username of the responsible team member).

Submission Guidelines

• Assignments will be checked on nova. You should build and test the assignment on nova environment before submission since that is where the programs will be checked for grading.
• The assignments will be copied automatically from the team account, on midnight of the submission due day. Directory and file names will be specified in each assignment. 
• The permissions of the entire path from your home directory down to the assignment files themselves should be 705. Make sure we can copy your files, but other students cannot.
• Your code must compile without warnings.
• Assignments will be check both manually and automatically.
• Automatic checker will run the program on inputs provided with each assignment and additional inputs. The output will be compared to the output of the reference compiler using "diff".
• Your best bet is to thoroughly test your program on the provided inputs, and make up others of your own until you feel confident in your results. We will not spend a lot of time examining your source and/or giving design feedback. It is not that we don't consider style or design is important, but by now all of you have taken other courses and we hope you have internalized and practice good coding practices as a matter of habit. Thoughtful design and coding will improve your chances of having a correctly working program, too.
• Please submit assignments on time. If  team members serve in the army during the semester, talk to me before you leave if you need an extension, and present an official confirmation when you are back.

Resources

• A special account on \\netapp\ was created for the compilation course. The username for the account is ~compiler . This account contains some reasources that you might find useful for your project assignments. Currently, the following resources are available:
  • ~compiler/COOL_DIR/bin/coolc - a binary (executable) of the cool compiler.
  • ~compiler/COOL_DIR/bin/spim - a binary (executable) of the MIPS simulator.
  • ~compiler/COOL_DIR/bin also contains reference binaries for each of the 4 phases of the COOL compiler: lexer, parser, semant, cgen. The script mycoolc in the same directory combines these phases using pipe mechanism.
    > You can test your implementation of PA2-PA5 by comparing its output to the output of the corresponding binary.
  • ~compiler/COOL_DIR/examples - a few small and not so small example programs which illustrate various aspects of the Cool programming language, also available here. You might find it useful when implementing PA1.

• The Cool Reference Manual

• JavaDoc of Cool Support Files

• Documentation of the Cool Runtime System (with Coolaid additions): [PS] [PDF]

• Coolaid Reference Manual: [PS] [PDF]
• The theory behind Coolaid: [PDF]

• References on JLex and JavaCup:
  • JLex Homepage
  • JLex Manual
  • JFlex Homepage
  • JavaCup old homepage
  • JavaCup new homepage
  • JavaCup Manual
  • JLex & JavaCup Tutorial
  • JLex lecture notes from Ras Bodik's class
  • Parsing with JavaCup tricks
• References on MIPS & SPIM:
  
  • A PDF version of the SPIM Manual (appendix from Hennessy & Patterson's architecture book)
  • The SPIM home page (downloadable versions, more docs).
  • MIPS tutorial
• Java
  • Java tutorial @ Sun
  • Another tutorial
  • Java FAQ, in particular see item E5 which is a common pitfall
  • Eclipse IDE
  • Wikipedia article on Object Oriented Programming
  • Java Modeling Language
• Introduction guide on garbage collection techniques
• A short survey on garbage collection techniques

Cool Related Links

• Winter 2004-2005 Compilation course practice page (Greta Yorsh)
• Winter 2004-2005 Compilation course homepage (Mooly Sagiv)
• Winter 2002-2003 Compilation course homepage (Mooly Sagiv)
• Winter 2002-2003 Compilation course practice page (Eran Yahav)
• Cool Project Homepage
• CS143 - Compilers (Stanford)
• Compiler Design and Construction I (Wright State University)
• Compiler Design and Construction II (Wright State University)
• Programming Languages and Compilers, Spring 2006 (Berkeley)