Related articles |
---|
Two-pass C compilers maniattb@cs.rpi.edu (1992-08-15) |
Re: Two-pass C compilers behrenss@Informatik.TU-Muenchen.DE (1992-08-16) |
Re: Two-pass C compilers quanstro@stolaf.edu (1992-08-16) |
Re: Two-pass C compilers markh@csd4.csd.uwm.edu (1992-08-16) |
Re: Two-pass C compilers sasghm@unx.sas.com (Gary Merrill) (1992-08-17) |
Re: Two-pass C compilers leichter@zodiac.rutgers.edu (1992-08-18) |
Re: Two-pass C compilers mcrware!adam@uunet.UU.NET (1992-08-19) |
Newsgroups: | comp.compilers,comp.lang.c |
From: | behrenss@Informatik.TU-Muenchen.DE (Soenke Behrens) |
Organization: | Technische Universitaet Muenchen, Germany |
Date: | Sun, 16 Aug 1992 13:21:15 GMT |
References: | 92-08-081 |
Keywords: | C |
Hmmm ... beat me if I something silly, but: Is there any way around
a two-pass compiler? (Or even more passes)
First pass: Reading in the source, preprocessing it, building a symbol table.
Second pass: Generate p-Code
Third pass: Optimize p-Code (Note: Do not mix with 2nd pass or you are
in deep trouble)
Fourth pass: Generate native code in linkable object file
Soenke
--
behrenss@informatik.tu-muenchen.de
FIDO: 2:246/13 Soenke Behrens
[I would call those compiler phases, and use "pass" to mean reading the source
code. A classic two-pass assembler reads the source once to establish values
for the symbols and again to generate object code and maybe a listing using
the symbol values. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.