Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| 50 times longer to compile than copy smnsn@my-deja.com (2000-11-04) |
| Re: 50 times longer to compile than copy ian@jawssystems.com (2000-11-05) |
| Re: 50 times longer to compile than copy vii@penguinpowered.com (John Fremlin) (2000-11-05) |
| Re: 50 times longer to compile than copy s337240@student.uq.edu.au (Trent Waddington) (2000-11-05) |
| Re: 50 times longer to compile than copy chase@naturalbridge.com (David Chase) (2000-11-07) |
| Re: 50 times longer to compile than copy Sid-Ahmed-Ali.TOUATI@inria.fr (Sid Ahmed Ali TOUATI) (2000-11-07) |
| Re: 50 times longer to compile than copy ONeillCJ@logica.com (Conor O'Neill) (2000-11-09) |
| Re: 50 times longer to compile than copy lex@cc.gatech.edu (Lex Spoon) (2000-11-09) |
| Re: 50 times longer to compile than copy christl@belinda.fmi.uni-passau.de (2000-11-09) |
| Re: 50 times longer to compile than copy jacob@jacob.remcomp.fr (jacob navia) (2000-11-09) |
| [1 later articles] |
| From: | Trent Waddington <s337240@student.uq.edu.au> |
| Newsgroups: | comp.compilers |
| Date: | 5 Nov 2000 20:51:36 -0500 |
| Organization: | University of Queensland |
| References: | 00-11-034 |
| Keywords: | performance, comment |
It is also important to remember that many intermediate files are
written to disk by most unix compilers: The input to the assembler and
the object file input to the linker. Plus there is the reading of the
c link time library (which can be very big if you are linking
statically). Depending on your processor speed, I agree that most of
your time in compiling should be spent on I/O.
Trent
[There are certainly intermediate files, but their size should be roughly
a linear function of the size of the input. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.