Bug#194345: Please update status for reports #194345 and #194513

[Matt Zimmerman <mdz@debian.org>]

On Sat, Jan 31, 2004 at 08:32:51PM +0100, Matthias Klose wrote:

> Please could you recheck the status of the two reports with current
> gcc-3.3 from unstable, and if you see the same behaviour, try to
> reproduce it with gcc-snapshot (gcc-3.4)?

I still see the same memory consumption with current 3.3 that I did before.
There is a source file in mythtv which requires over nearly 200M for g++ to
compile.

mdz      17294 88.4 34.6 185244 178696 pts/4 R    12:12   2:10 /usr/lib/gcc-lib/i486-linux/3.3.3/cc1plus

gcc-snapshot seems to fare much better, though still rather high for many
systems.  The highest usage I noticed was:

mdz      17478 92.1 26.0 138592 134248 pts/4 R    12:16   0:39 /usr/lib/gcc-snapshot/libexec/gcc/i486-linux/3.4.0/cc1plus

But as a pleasant surprise, it completed in much, much less time.

gcc-3.3: 151.93user 3.48system 2:38.55elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1697major+208633minor)pagefaults 0swaps

gcc-snapshot: 41.28user 0.46system 0:42.33elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1267major+46254minor)pagefaults 0swaps


-- 
 - mdz