Related articles |
---|
lcc intel backend? nick@nsis.cl.nec.co.jp (1993-10-07) |
Re: lcc intel backend? compile time? rds95@csc.albany.edu (1993-10-13) |
Re: lcc intel backend? compile time? graham@pact.srf.ac.uk (1993-10-13) |
Re: lcc intel backend? compile time? cliffc@rice.edu (1993-10-13) |
Re: lcc intel backend? compile time? rds95@csc.albany.edu (1993-10-13) |
Re: lcc intel backend? compile time? pardo@cs.washington.edu (1993-10-20) |
Re: lcc intel backend? compile time? henry@zoo.toronto.edu (1993-10-20) |
Re: lcc intel backend? compile time? tchannon@black.demon.co.uk (1993-10-21) |
Re: lcc intel backend? compile time? henry@zoo.toronto.edu (1993-10-22) |
Newsgroups: | comp.compilers |
From: | cliffc@rice.edu (Cliff Click) |
Keywords: | C, performance |
Organization: | Center for Research on Parallel Computations |
References: | 93-10-041 93-10-059 |
Date: | Wed, 13 Oct 1993 17:18:17 GMT |
(Gavin Thomas Nicol) writes:
> [fast compilation...] makes [lcc] ideal for the development stages where
>fast compile times are more important than good code [...]
rds95@csc.albany.edu (Robert Seals) writes:
> This has been the conventional wisdom for at least as long as I can
> remember (so I'm young). But frankly, I've never had undue difficulty with
> the compile time of small-to-medium programs ...
My experience is that there is a quantum leap in productivity when
compile/link times fall from 5-10 seconds down to < 0.5 seconds. With
extremely fast compile/links programmers are willing to "experiment" more,
try other approaches, try more debugging tests, and fine tune their code.
The result is faster, tighter code with fewer bugs. In short, your
programming thought processes are not 'put on hold' while the compiler
grinds.
Warning: Small sample size!
I witnessed this on 2 different teams, each with 3-6 programmers (number
varied over time). Each team used a different tool(s) to get the fast
compile/link times.
Cliff
--
cliffc@cs.rice.edu -- Massively Scalar Compiler Group, Rice University
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.