|Compiler construction projects firstname.lastname@example.org (Roderick Bloem) (2005-06-02)|
|Re: Compiler construction projects email@example.com (TOUATI Sid) (2005-06-02)|
|Re: Compiler construction projects firstname.lastname@example.org (Laurence Finston) (2005-06-02)|
|Re: Compiler construction projects email@example.com (2005-06-10)|
|Re: Compiler construction projects firstname.lastname@example.org (2005-06-12)|
|Re: Compiler construction projects email@example.com (Gene) (2005-06-19)|
|Re: Compiler construction projects firstname.lastname@example.org (Oliver Bandel) (2005-06-23)|
|Re: Compiler construction projects email@example.com (Skandinavisches Seminar) (2005-06-26)|
|From:||TOUATI Sid <firstname.lastname@example.org>|
|Date:||2 Jun 2005 14:59:05 -0400|
|Organization:||Universite de Versailles Saint-Quentin-en-Yvelines|
I am another teacher of compilation in trhe first year of master.
The compilation project changes every year.
But usually, we ask students to work inside groups of four people to
build a C compiler to x386 codes. For more modulariry, the students must
implement two major modules :
- a front end from a C lanaguage to a three-adress C-code.
- a backend from the three-adress C-code to x386 asm code.
Decomposing the project into two parts allow to the students to have
something that work if they do not succeed in building the whole compiler.
We use a subset of C language (C without pointers, C without arrays,
etc.). Parsing a code generation are done with lex&yacc.
According to our experience, good students always succeed in building
such compiler. But "middle" students do not succeed : usually, front end
or backend work but not both.
Return to the
Search the comp.compilers archives again.