cc1 hog

[Robert Lipe]

> > Running /src/egcs-970929/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
> >   PID USERNAME PRI NICE   SIZE   RES STATE   TIME   WCPU    CPU COMMAND
> >  3538 neal      -5    0 83388K 42732K sleep   0:12 18.27% 16.34% cc1
> 
> Perhaps we need to enhance dejagnu to add memory limits, and count tests
> as failing if they exceed a certain amount of memory.  Otherwise we won't
> immediately notice when a change suddenly explodes the amount of memory

Becuase OpenServer handles the 961203 "I'm going to eat every byte of VM
I can find" failure, er, ungracefully, I found that just running runtest
under ksh so I could use ulimit to cap VM usage, core file size, and stack
size was a big help.   If the compiler got too big, the OS killed it and
it shows up as a runtest failure - exactly what I wanted.

Of course, deciding "how big is too big, while still allowing 'big enough'"
is an exercise left for the astute reader.  I know that I arbitraily picked
a number and found that many mysterious c-torture faliures were actually
becuase the number I picked was too low.

RJL