Tree-ssa status with POOMA

[Richard Guenther]

On Thu, 5 Feb 2004, Jan Hubicka wrote:

> > On Thu, 2004-02-05 at 07:14, Richard Guenther wrote:
> >
> > > > It would also suggest that the inline limits are still bit too up for
> > > > 3.4.  How did you measured the memory usage?
> > >
> > > I did look at "top" output - do you have some better way to record maximum
> > > RSS size?
> > >
> > Not really.  I typically do
> >
> > $ top -b > log &
> > $ gcc ...
> > $ kill %1
> >
> > and then use grep/sort/awk to get data from the log.
> I do similar trick, but the problem is that GGC sets watermarks for heap
> size according to available memory, unless GCC is compiled with
> checking, so the results are mixture of peak usage, overall conumption,
> memory size and random effect on when the GGC has been invoked,
> resulting in not very informative numbers.

Well - the number usually _is_ interesting for me, as if ggc can't help
and gcc goes into swap, I'm very unhappy ;)  And for comparisons on the
same machine it is ok, too.  But I never found -fmem-report useful, as
it doesn't tell me it needed 1.2Gigs of ram and gone into swap, but always
had numbers way lower. Like

Total        348M        214M       3409k

for a compilation requiring ~900MB of ram.

Richard.

--
Richard Guenther <richard dot guenther at uni-tuebingen dot de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/