COP5621: Compiler Construction

COP5621 Compiler Construction

Spring 2008

Meeting time Monday, Wednesday, 2:00pm-3:15pm

Meeting location 103 Lov Building

Instructor Prof. Xin Yuan, 168 Love Building, 644-9133, xyuan@cs.fsu.edu

Office hours Monday, Wednesday 1:00pm-2:00pm, Tuesday 1:00pm-3:00pm, or by appointment.

Textbook Compilers Principles, Techniques and Tools, by Alfred V. Aho, Ravi Sethi and Jeffrey D. Ullman

Class Home Page http://www.cs.fsu.edu/~xyuan/cop5621/index.html

Course description and objectives

This course introduces basic techniques in compiler construction. It focuses on the compiler front-end, including lexical analysis, syntax analysis, syntax-directed translation, semantic analysis and code generation.

In this course, you are expected to:

Understand the theories and techniques in each phase of the compiler front-end.
Master tools (lex and yacc) for constructing a compiler.
Apply key implementation techniques to construct a working compiler.

Prerequisite

Unofficial note: This is a programming intensive course: you will need to write a whole compiler for a not-so-simple language. This compiler will consist of around 5000 lines of code. You should be proficient in C/C++. You should also know (or self-learn) x86 or SPARC assembly.

Assignments, Projects & Exams

Homework will be assigned from the textbook or via handouts, quizzes will be given randomly with or without prior notification. Homework assignments must be submitted in hard-copies. Electronic mail submissions are NOT accepted. There will be one midterm and one final. Make-up exams will be given with a valid reason AND the prior consent of the instructor. There will be one programming project that is composed of four phases: lexical analysis (using lex), syntax analysis (using yacc), semantic analysis, and code generation (for x86 or SPARC).

The final grade will be computed as follows

H = (H₁ + ... + H_m-1 + H_m + Q₁ + Q₂ + ... + Q_k) / (m+k) Homework/Quiz average

P = P₁*10% + P₂*20% +P₃*30% +P₄*40% Project average, this formula may change

E = MT*40% + FINAL * 60% Exam average

if (E < threshold(tentatively 60)) then

G = min{P, E}

else

G =P*50%+E*40%+H*10% Final grade

Final letter grade will be assigned based on the relative performance. A student ranked in top 10% in the class will guarantee an A. Like a typical graduate class, it is expected that half of the class will receive A or A- grades.

Tentative Schedule

Week 1: Class outline, Introduction and overview (Chapter 1, 2)
Week 2: overview and lexical analysis (Chapter 3).
Week 3: Lexical analysis (Chapter 3), project phase 1 out.
Week 4: Syntax analysis (Chapter 4).
Week 5: Syntax analysis (Chapter 4), project phase 1 due, phase 2 out.
Week 6: Syntax analysis (Chapter 4).
Week 7: Syntax directed translation(Chpater 5).
Week 8: Syntax directed translation (Chapter 5), Project phase 2 due, phase 3 out.
Week 9: Type Checking (Chapter 6), Midterm.
Week 10: Spring Break.
Week 11: Run-time Environment (Chapter 7), Project phase 3 due, Project phase 4 out.
Week 12: Run-time Environment (Chapter 7) and Intermediate Code Generation (Chapter 8)
Week 13: Intermediate Code Generation (Chapter 8)
Week 14: Intermediate Code Generation (Chapter 8)
Week 15: Code generation and optimization (Chapter 9, 10).
Week 16: Final Exam Week.

Academic Honor Code

You are required to read the FSU Academic Honor Code and abide by it. First violations will result in a 0 for the particular item and the lowering of the final course grade by one letter (e.g. B+ --> C+). Repeat violations will result in a grade of F.

By turning in work for a grade in this course you are representing it as being entirely your own individual work. Unless otherwise specified in writing, all programming projects are individual projects. If any assignment permits teamwork, it will be explicitly stated so in the assignment, and then the work is required to be only the work of the people on the team.

What does ``individual work'' mean? An intelligent person searches publications (including the web) for information, ideas, and code. If you use information or ideas obtained from the work of another person you must at least give credit via comments in your code stating what you have used, where you obtained it, and who is the person to whom credit is due. (Beware: If an idea is patented the above is not enough; you should not use it at all without a license.) If you use any code written by another person you must first obtain permission from the author or copyright owner, then mark the beginning and end of the quoted code using appropriate comments, and include a comment giving where you found the code and the the name of the author or copyright holder. Failure to follow these rules will be considered a violation of the Academic Honor Code.

Accommodation for Disabilities

Students with disabilities needing academic accommodations should:

Register with and provide documentation to the Student Disability Resource Center (SDRC).
Bring a letter to the instructor from the SDRC `indicating you need academic accomodations. This should be done within the first week of class.

This syllabus and other class materials are available in alternative format upon request.

For more information about services available to FSU students with disabilities, contact the Assistant Dean of Students:

Student Disability Resource Center
08 Kellum Hall
Florida State University
Tallahassee, FL 32306-4066

e-mail: sdrc@admin.fsu.edu
phone: (850) 644-9566.