Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| GCC vs. Turbo C performance stt@inmet.inmet.com (1990-11-28) |
| Re: GCC vs. Turbo C performance moss@cs.umass.edu (1990-12-01) |
| Newsgroups: | comp.compilers |
| From: | stt@inmet.inmet.com |
| Nf-Id: | #R:<9011232019.AA14958@milton.u.was:-44:inmet:19400004:000:443 |
| Old-Subject: | Re: Recursive Descent Parsers and YACC |
| Keywords: | performance, GCC |
| Organization: | Compilers Central |
| Nf-From: | inmet.inmet.com!stt Nov 28 14:55:00 1990 |
| Date: | 28 Nov 90 19:55:00 GMT |
Re: time spent in GCC's "parse" phase.
I would assume that this "parse" phase is actually the entire front-end.
I doubt if they separate out the time actually spent walking the parse
tables themselves. I agree with others that this aspect is not a big
deal. Turbo C and Think C probably get their speed by doing most of the
front-end processing while the user is typing in the program.
S. Tucker Taft
Intermetrics, Inc.
Cambridge, MA 02138
[Turbo is a conventional compiler that compiles regular old ASCII source files
into binary code. It buffers entire files in memory, compiles directly to
object code without a separate assembler step, and uses a very fast and
simple linker. Nothing exotic, just good engineering. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.