Re: Semantic difference of source files

glen herrmannsfeldt <gah@ugcs.caltech.edu>
Wed, 20 Aug 2008 12:50:45 -0800

          From comp.compilers

Related articles
Semantic difference of source files m.helvensteijn@gmail.com (Michiel) (2008-08-17)
Re: Semantic difference of source files m.helvensteijn@gmail.com (Michiel) (2008-08-17)
Re: Semantic difference of source files barry.j.kelly@gmail.com (Barry Kelly) (2008-08-18)
Re: Semantic difference of source files DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-08-18)
Re: Semantic difference of source files gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-08-18)
Re: Semantic difference of source files gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-08-19)
Re: Semantic difference of source files marcov@stack.nl (Marco van de Voort) (2008-08-20)
Re: Semantic difference of source files gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-08-20)
Re: Semantic difference of source files DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-08-23)
Re: Semantic difference of source files marcov@stack.nl (Marco van de Voort) (2008-08-24)
Re: Semantic difference of source files Jatin_Bhateja@mentor.com (Jatin Bhateja) (2008-08-28)
Re: Semantic difference of source files m.helvensteijn@gmail.com (2008-08-28)
| List of all articles for this month |

From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: comp.compilers
Date: Wed, 20 Aug 2008 12:50:45 -0800
Organization: Compilers Central
References: 08-08-025 08-08-030
Keywords: performance
Posted-Date: 23 Aug 2008 14:42:04 EDT
X-Usenet-Provider: http://www.giganews.com

Hans-Peter Diettrich wrote:
(snip)


> Some languages IMO still compile very slowly. Where I can do a "make"
> in Delphi, in order to only find the next error in my code, C++ coders
> still complain about hours of compilation for huge projects.


One complication with C and C++ is that some variables have file
scope. Even if none do, the compiler has to be able to compile them,
and so tends to keep data in memory (or backing store) through the
whole file. Many functions in one file compile slower than they would
as separate files.


Fortran compilers traditionally reinitialize just about everything on
an END statement, before starting the next program unit. I believe
the standard has been changed, but in the past compilers did that so
well that a comment after the last END would start a new program unit.
The result was many error messages, such as missing END statement, and
duplicate MAIN program at link time.


-- glen



Post a followup to this message

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