i used the file compiletimetest2.cc from the attachment in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
and noticed that compile time regressions were introduced after
gcc-4.0-20050430
i added the timings for the 4.0 snapshots to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
because there are also many older time reports.
now here for gcc-4.1-20050508
> gcc-4.1-20050508 -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.1-20050508/configure --prefix=/opt/gcc-4.1-20050508
--program-suffix=-4.1-20050508 --enable-shared --enable-languages=c,c++
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--disable-nls --disable-checking --with-arch=pentium3
Thread model: posix
gcc version 4.1.0 20050508 (experimental)
> time g++-4.1-20050508 -c -O3 -D __NDEBUG__ cotime g++-4.1-20050508 -c -O3 -D
__DEBUG__ compiletimetest2.cc
real 1m47.056s user 1m45.474s sys 0m1.392s
> time g++-4.1-20050508 -c -O3 -D __DEBUG__ compiletimetest2.cc
real 1m53.201s user 1m51.746s sys 0m1.319s
> g++-4.1-20050508 -c -O3 -D __NDEBUG__ compiletimetest2.cc -save-temps
> ls -al compiletimetest2.s
-rw-r--r-- 1 login500 users 1602910 May 8 23:20 compiletimetest2.s
the assembler file increased once more now 1.603 mb, gcc-3.4.3 (0.520mb),
gcc-3.3.5 (0.355mb)
gcc-3.4.3 did the whole thing in under 20s.
gcc-3.3.5 under 11s
i know i'm using -O3. But you see, this is almost a factor of 8.5.
Regards Andre
--
Summary: compile time regression(s) after gcc-4.0-20050326, 4.0
(+300%) 4.1 (+500%)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: regression
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: andre dot maute at gmx dot de
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21456
