This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/984: GCC cannot efficently initialize a big array
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, wscott at ichips dot intel dot com
- Date: 10 Nov 2002 20:59:55 -0000
- Subject: Re: c++/984: GCC cannot efficently initialize a big array
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, wscott at ichips dot intel dot com, gcc-gnats at gcc dot gnu dot org
Synopsis: GCC cannot efficently initialize a big array
State-Changed-From-To: analyzed->closed
State-Changed-By: bangerth
State-Changed-When: Sun Nov 10 12:59:54 2002
State-Changed-Why:
Someone seems to have ported the C part to C++. With today's
CVS, I see (for only 5000 elements):
tmp/g> perl bigarry.pl > x.cc
tmp/g> cp x.cc x.c
tmp/g> time /home/bangerth/bin/gcc-3.3x-pre/bin/gcc -c x.c
real 0m24.119s
user 0m10.600s
sys 0m0.520s
tmp/g> time /home/bangerth/bin/gcc-3.3x-pre/bin/gcc -c x.cc
real 0m31.587s
user 0m14.330s
sys 0m0.550s
And I get a peak memory use of 140MB for the C front end
and 175 MB for the C++ front end. This seems to be in the
usual range of increase when moving from C to C++.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=984