Re: Fast code vs. fast compile

John Lilley <jlilley@empathy.com>
22 Jan 1997 00:03:58 -0500

          From comp.compilers
Related articles
Beginner's Question... mihai@A-aod.resnet.ucsb.edu (Mihai Christodorescu) (1997-01-16)
Fast code vs. fast compile dennis@netcom.com (1997-01-16)
Re: Fast code vs. fast compile salomon@silver.cs.umanitoba.ca (1997-01-19)
Re: Fast code vs. fast compile darius@phidani.be (Darius Blasband) (1997-01-22)
Re: Fast code vs. fast compile jlilley@empathy.com (John Lilley) (1997-01-22)
Re: Fast code vs. fast compile mwolfe@dat.cse.ogi.edu (1997-01-22)
Re: Fast code vs. fast compile mikey@ontek.com (1997-01-22)
Re: Fast code vs. fast compile conway@cs.mu.oz.au (1997-01-22)
Re: Fast code vs. fast compile darius@phidani.be (Darius Blasband) (1997-01-25)
Re: Fast code vs. fast compile wws@renaissance.cray.com (Walter Spector) (1997-01-25)
Re: Fast code vs. fast compile kanze@gabi-soft.fr (1997-02-16)
| List of all articles for this month |
From: John Lilley <jlilley@empathy.com>
Newsgroups: comp.compilers
Date: 22 Jan 1997 00:03:58 -0500
Organization: Nerds for Hire, Inc.
References: 97-01-122 97-01-137 97-01-159
Keywords: performance, practice

Dennis Yelle <dennis@netcom.com> wrote:
|> As a compiler user, I am (almost) always more concerned about fast
|> code rather than fast compilation.


Daniel J. Salomon wrote:
> Actually the two speeds, compilation versus execution, are sometimes
> related.


Compilation and executation speed are also related as follows: The
less time I spend waiting for the compiler or otherwise wrestling with
unproductive tools (debuggers, doc systems, source code control,
xrefs, etc -- not to say that such tools are necessarily
unproductive), the less time I have available to spend on other
optimizations. A quality compiler produces optimizations of a certain
sort. Other source-code optimization techniques (caching, improving
basic algorithms, reference-counting, rewriting bottlenecks) are
sometimes better.


john lilley
--

Post a followup to this message

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