Re: Compiler Construction - New to it and getting started.

TOUATI Sid <touati@nospam-prism.uvsq.fr>
28 Feb 2005 00:52:45 -0500

          From comp.compilers
Related articles
Compiler Construction - New to it and getting started. NatLWalker@gmail.com (Nate the Capricious) (2005-02-11)
Re: Compiler Construction - New to it and getting started. napi@cs.indiana.edu (2005-02-12)
Re: Compiler Construction - New to it and getting started. torbenm@diku.dk (2005-02-16)
Re: Compiler Construction - New to it and getting started. touati@nospam-prism.uvsq.fr (TOUATI Sid) (2005-02-28)
Re: Compiler Construction - New to it and getting started. torbenm@app-4.diku.dk (2005-02-28)
Re: Compiler Construction - New to it and getting started. touati@prism.uvsq.fr (TOUATI Sid) (2005-03-01)
| List of all articles for this month |
From: TOUATI Sid <touati@nospam-prism.uvsq.fr>
Newsgroups: comp.compilers
Date: 28 Feb 2005 00:52:45 -0500
Organization: Universite de Versailles Saint-Quentin-en-Yvelines
References: 05-02-039 05-02-068
Keywords: practice
Posted-Date: 28 Feb 2005 00:52:45 EST

Right,
I would suggest Ocaml as a programming language for a clean compiler.
But, if the compiler would do some backend or advanced code
optimization, I think that Ocaml wouldn't be the best choice.


As I tell to my students, compilation can be seen as a formal work
when doing simple parsing&semantic analysis&simple code generation.
Unfortunately, many code optimization techniques in the litterature
are completely ad-hoc, and no formal description/model can be easily
used. Such ad-hoc techniques require to "hack" a compiler or to use
some "C" programming inside the compiler. While this is not the best
thing for a compiler, this is actually the situation of (maybe) almost
all optimizing compilers.


S

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.