|how to increase compilation performance email@example.com (Thomas Gänshirt) (1999-02-05)|
|Re: how to increase compilation performance firstname.lastname@example.org (1999-02-07)|
|Re: how to increase compilation performance email@example.com (Charles E. Bortle, Jr.) (1999-02-10)|
|Re: how to increase compilation performance firstname.lastname@example.org (Charles.E.Bortle@dfw-ixnews9.ix.netcom.com,Jr.) (1999-02-12)|
|Re: how to increase compilation performance email@example.com (Stephen J Bevan) (1999-02-15)|
|From:||firstname.lastname@example.org (Richard Weaver)|
|Date:||7 Feb 1999 00:12:40 -0500|
For approaches to a similar problem, look for references to
interpreters that support execution time editing of the source. The
IBM PL/I Checkout Compiler was one such; I have no recollection of what
is in the general literature.
John's answer is better, however. You might also look at why users are
constructing source programs requiring a lot of time to compile, as
opposed to using function/subroutine/procedure/module/... facilities to
organize their source code into smaller units.
And profile the complete process, when someone makes only "a little"
change it is not just the compiler that is involved. Look at all the
steps necessary to get the revised code executing.
>I have implemented a compiler for ST/IL running on an automation
>system. Now I have the job to make the compiler as fast as possible
>for the case, that a programmer changes his source only "a little". An
>idea was to split the source into small pages and only to rebuild the
>modified and affected ones.
Return to the
Search the comp.compilers archives again.