Re: Semantic difference of source files

glen herrmannsfeldt <gah@ugcs.caltech.edu>
Mon, 18 Aug 2008 14:12:16 -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)
[1 later articles]
| List of all articles for this month |

From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: comp.compilers
Date: Mon, 18 Aug 2008 14:12:16 -0800
Organization: Compilers Central
References: 08-08-025
Keywords: parse, practice
Posted-Date: 19 Aug 2008 22:19:19 EDT

(snip, John wrote:)


> The question of why nobody seems to care about compilation speed any
> more. -John]


I wonder more about why nobody cares about compilation memory
requirements. For time, you can always wait, but if you don't have
enough memory you are stuck. (Or virtual address space in the case of
virtual memory.)


The art of compiling large programs on small machines seems to be
completely lost.


-- glen
[Good point. I hear that GCC can no longer compile itself
on mainframe IBM 360 MVS because it doesn't fit. -John]



Post a followup to this message

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