This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Wednesday 07 July 2004 17:48, Richard Guenther wrote:
The automated POOMA/tramp3d tester at http://www.tat.physik.uni-tuebingen.de/~rguenth/gcc/monitor-summary.html now tracks the maximum used virtual memory of cc1plus of mainline, too. As a first "hint", today it revealed that mainline needs about 1GB of ram compared to 3.4.1 which needs only 625MB. This is on ia64 for the tramp3d-v3.cpp testcase at -O2 -funroll-loops -ffast-math with the leafify patch included.
I get the attached timings and memory used on i686 (with memory use "measured" with 'top') on a machine with 3GB RAM, gcc configured with
* --disable-{nls,libmudflap,checking} --enable-languages=c,c++ * your leafify patch applied * command line: ./libexec/gcc/i686-pc-linux-gnu/3.5.0/cc1plus \ -iprefix /abuild/stevenb/lib/gcc/i686-pc-linux-gnu/3.5.0/ -D_GNU_SOURCE \ tramp3d-v3.cpp -dumpbase tramp3d-v3.cpp -mtune=pentium3 \ -auxbase tramp3d-v3 -version -o /tmp/cccsWqOw.s $FLAGS
Where $FLAGS is the flags indicated before the time report...
I did not use -quiet, I wanted to see how much memory we collect. Not a surprise that it doesn't collect often, and when it does, it collects lots, e.g. numbers like {GC 445994k -> 236931k} are not unusual.
We consume a lot more time in 'integration' than I expected...
Gr. Steven
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |