ESIX neophyte has questions

[david nugent]

In <PCG.90Jul4113012 at odin.cs.aber.ac.uk> pcg at cs.aber.ac.uk (Piercarlo Grandi) writes:


>   2. Gcc compiles with /bin/cc, but fails to compile itself, apparently
>   looping when attempting to compile c-parse.tab.c.  The stock cc compiles
>   this particular file pretty quickly, and I let gcc munch on it for over
>   eight hours.  Has anybody gotten gcc to compile itself?

>You must have at least 4 megabytes of memory to run gcc with the
>optimizer on. Gcc grows to several megs, and has very poor locality, and
>gets paged. Worse, it gets swapped mercilessly because of a mistake in
>the ESIX swapper algorithm.


Using a system with 4 megs of memory under Interactive, I ran into this 
same problem with gcc.  I recompiled that particular module with cc, and
continued to the next stage.  The second compiled version of gcc DID 
compile this module, though it still took over 5 minutes.  I put this
down to a problem with /bin/cc rather than gcc itself.

As an excercise, I later built gcc from scratch (due to some other problems
I was having with some code it produced, which /bin/as barfed on), but on
the first compile with gcc hit the same problem.  This time, I recompiled
that module by hand with gcc, ommitting the -O.  Worked fine.  The
second compile also worked without interference.

So right now, I don't know what to put it down to.  I can concur that it
_must_ be memory and the optimiser since during the time it was compiling
the machine was running like a dog, which didn't occur with the other
modules.


david

-- 
_______________________________________________________________________________
 Unique Computing Pty Ltd  Melbourne  Australia  -  Communications Specialists 
        david at csource.oz.au    3:632/348 at fidonet    28:4100/1 at signet