Re: GCC vs. Turbo C performance

>>>>> On 28 Nov 90 19:55:00 GMT, stt@inmet.inmet.com said:
Taft> Re: time spent in GCC's "parse" phase.


Taft> ... Turbo C and Think C probably get their speed by doing most of the
Taft> front-end processing while the user is typing in the program.


I don't think so. The compiler runs separately from the editor and really does
read all the source file(s) from disk. I think they get most of their speed
by hand coding a lot of crucial routines in assembly, and by focusing on speed
in designing their compilers. My guess is that they feel it is a market very
sensitive to this issue, and hence worth the effort. (It's also worth the
effort because of the profit and volume.)
--
J. Eliot B. Moss, Assistant Professor
Department of Computer and Information Science
Lederle Graduate Research Center
University of Massachusetts
Amherst, MA 01003
(413) 545-4206; Moss@cs.umass.edu
--

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