Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!wuarchive!hsdndev!spdcc!iecc!compilers-sender
From: stt@inmet.inmet.com
Newsgroups: comp.compilers
Subject: GCC vs. Turbo C performance
Keywords: performance, GCC
Message-ID: <19400004@inmet>
Date: 28 Nov 90 19:55:00 GMT
Sender: compilers-sender@iecc.cambridge.ma.us
Reply-To: stt@inmet.inmet.com
Organization: Compilers Central
Lines: 18
Approved: compilers@iecc.cambridge.ma.us
Nf-ID: #R:<9011232019.AA14958@milton.u.was:-44:inmet:19400004:000:443
Nf-From: inmet.inmet.com!stt    Nov 28 14:55:00 1990
Old-Subject: Re: Recursive Descent Parsers and YACC

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]
-- 
Send compilers articles to compilers@iecc.cambridge.ma.us or
{ima | spdcc | world}!iecc!compilers.  Meta-mail to compilers-request.