Re: c++/984: GCC cannot efficently initialize a big array

Re: c++/984: GCC cannot efficently initialize a big array

[jason]

Synopsis: GCC cannot efficently initialize a big array

State-Changed-From-To: open->analyzed
State-Changed-By: jason
State-Changed-When: Wed Mar 20 02:54:39 2002
State-Changed-Why:
    The C frontend was modified several years ago to handle large initializers like this efficiently, but nobody has ported the changes to the C++ frontend.  Until that happens, you could compile your array in a separate C source file.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=984

Re: c++/984: GCC cannot efficently initialize a big array

[bangerth]

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