Re: Speedy compilers (Ken Walter)
30 Nov 1998 02:10:37 -0500

          From comp.compilers

Related articles
[2 earlier articles]
Re: Speedy compilers (1998-11-19)
Re: Speedy compilers (Jack W. Crenshaw) (1998-11-19)
Re: Speedy compilers (Toon Moene) (1998-11-21)
Re: Speedy compilers (Joachim Durchholz) (1998-11-24)
Re: Speedy compilers (Andrew Fry) (1998-11-24)
Re: Speedy compilers (Robert Bernecky) (1998-11-24)
Re: Speedy compilers (1998-11-30)
Re: Speedy compilers (Janusz Szpilewski) (1998-11-30)
Re: Speedy compilers (Amit Patel) (1998-12-10)
Re: Speedy compilers (1998-12-13)
Re: Speedy compilers (1998-12-18)
Re: Speedy compilers (1998-12-18)
Re: Speedy compilers (1998-12-18)
[8 later articles]
| List of all articles for this month |

From: (Ken Walter)
Newsgroups: comp.compilers
Date: 30 Nov 1998 02:10:37 -0500
Organization: Solution Technology
References: 98-11-047 98-11-086 98-11-089 98-11-115
Keywords: performance

> [ re the lesson that customers want fast compilers ]
> The lesson still applies, but there is no fast C++ compiler on Windows
> (not because C++ is slow but because these compilers all include
> megabytes of Windows header files by default). I think a compiler
> that uses precompilation in a sensible manner will blow the socks off
> all existing C++ compilers. For example, by keeping a precompiled file
> for every source file instead of a single precompiled header that has
> to fit all sources. Even better would be a segmented precompiled file
> that could restart compilation in increments of, say, 1000 lines
> (i.e. dump out the compiler state every 1000 LOC, and for each new
> compilation, look how far the source is unchanged and restart
> compilation at that point).

Take a look at the Visual Age C++ 4.0 compiler when it comes out. It
has incremental compiling for only what you have changed along with
precompiled headers.

Ken Walter

Post a followup to this message

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