public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* compile time regression, when adding cerr usage
@ 2004-07-17 21:06 andre maute
2004-07-27 0:57 ` James E Wilson
2004-12-10 22:11 ` [Bug rtl-optimization/16613] [3.4 Regression] " andre maute
0 siblings, 2 replies; 13+ messages in thread
From: andre maute @ 2004-07-17 21:06 UTC (permalink / raw)
To: gcc-bugs
[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]
when compiling the attached test file, you can see that the debugging test
needs
8 min! with g++-3.4.1
Every other test including g++-3.3.3 needs only some seconds.
Defining __DEBUGGING__
enables the usage of std::cerr, which happens at the end of the attached file.
My system is a Dual Pentium III 550 with linux-2.4.26
Regards Andre
--------------- BEGINNING OF TESTS THE -------------------------
login:~ # /opt/gcc-3.3.3/bin/g++-3.3.3 -v
Reading specs from /opt/gcc-3.3.3/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/specs
Configured with: ../gcc-3.3.3/configure --prefix=/opt/gcc-3.3.3
--enable-shared --enable-languages=c,c++ --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --program-suffix=-3.3.3
--with-cpu=pentium3
Thread model: posix
gcc version 3.3.3
login:~ # time /opt/gcc-3.3.3/bin/g++-3.3.3 compiletimetest.cc -c -O3
-funroll-all-loops -frerun-loop-opt -fomit-frame-pointer
real 0m2.202s
user 0m2.150s
sys 0m0.030s
login:~ # time /opt/gcc-3.3.3/bin/g++-3.3.3 compiletimetest.cc -c -O3
-funroll-all-loops -frerun-loop-opt -fomit-frame-pointer -D __DEBUGGING__
real 0m5.202s
user 0m4.390s
sys 0m0.120s
login:~ # /opt/gcc-3.4.1/bin/g++-3.4.1 -v
Reading specs from /opt/gcc-3.4.1/lib/gcc/i686-pc-linux-gnu/3.4.1/specs
Configured with: ../gcc-3.4.1/configure --prefix=/opt/gcc-3.4.1
--enable-shared --enable-languages=c,c++ --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --program-suffix=-3.4.1
--with-cpu=pentium3
Thread model: posix
gcc version 3.4.1
login:~ # time /opt/gcc-3.4.1/bin/g++-3.4.1 compiletimetest.cc -c -O3
-funroll-all-loops -frerun-loop-opt -fomit-frame-pointer
real 0m6.670s
user 0m6.550s
sys 0m0.120s
login:~ # time /opt/gcc-3.4.1/bin/g++-3.4.1 compiletimetest.cc -c -O3
-funroll-all-loops -frerun-loop-opt -fomit-frame-pointer -D __DEBUGGING__
real 8m31.470s
user 7m53.460s
sys 0m34.400s
[-- Attachment #2: compiletimetest.cc.gz --]
[-- Type: application/x-gzip, Size: 13601 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: compile time regression, when adding cerr usage
2004-07-17 21:06 compile time regression, when adding cerr usage andre maute
@ 2004-07-27 0:57 ` James E Wilson
2004-07-27 8:00 ` andre maute
2004-12-10 22:11 ` [Bug rtl-optimization/16613] [3.4 Regression] " andre maute
1 sibling, 1 reply; 13+ messages in thread
From: James E Wilson @ 2004-07-27 0:57 UTC (permalink / raw)
To: andre maute; +Cc: gcc-bugs
andre maute wrote:
> when compiling the attached test file, you can see that the debugging test
> needs
> 8 min! with g++-3.4.1
> Every other test including g++-3.3.3 needs only some seconds.
We don't track bug reports sent to the gcc-bugs mailing list. If you
want something done about this, you should file a bug report into our
bugzilla bug database.
I took a quick look at this. You are using -O3 which enables
-finline-functions. The presense of the iostreams code causes gcc to
make different decisions about function inlining and optimization, and
the code size blows up. The .s file is almost 7 times as big when the
debugging code is included. So the file takes so much longer to compile
just because there is so much more code.
Part of the issue here might be that the debugging code is confusing the
gcc optimizer. It occurs between where the arrays are declared and
where they are used. Maybe there is an aliasing problem, or something,
that is causing some optimization to be missed, that ordinarily would
prevent the code size from blowing up. I didn't bother looking into
this though. All I did was reproduce the problem.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: compile time regression, when adding cerr usage
2004-07-27 0:57 ` James E Wilson
@ 2004-07-27 8:00 ` andre maute
2004-07-27 18:02 ` James E Wilson
0 siblings, 1 reply; 13+ messages in thread
From: andre maute @ 2004-07-27 8:00 UTC (permalink / raw)
To: James E Wilson; +Cc: gcc-bugs
On Tuesday 27 July 2004 02:57, you wrote:
> andre maute wrote:
> > when compiling the attached test file, you can see that the debugging
> > test needs
> > 8 min! with g++-3.4.1
> > Every other test including g++-3.3.3 needs only some seconds.
>
> We don't track bug reports sent to the gcc-bugs mailing list. If you
> want something done about this, you should file a bug report into our
> bugzilla bug database.
i already did that, see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
>
> I took a quick look at this. You are using -O3 which enables
> -finline-functions. The presense of the iostreams code causes gcc to
-fininline-functions is enabled in -O3 for both gcc-3.3.3 and gcc-3.4.1
> make different decisions about function inlining and optimization, and
> the code size blows up. The .s file is almost 7 times as big when the
> debugging code is included. So the file takes so much longer to compile
> just because there is so much more code.
but not with gcc-3.3.3
> Part of the issue here might be that the debugging code is confusing the
> gcc optimizer. It occurs between where the arrays are declared and
> where they are used.
Sorry that's wrong, cerr is declared at the beginning of the file and used at
the end of the file.
> Maybe there is an aliasing problem, or something,
> that is causing some optimization to be missed, that ordinarily would
> prevent the code size from blowing up. I didn't bother looking into
> this though. All I did was reproduce the problem.
Regards
Andre Maute
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: compile time regression, when adding cerr usage
2004-07-27 8:00 ` andre maute
@ 2004-07-27 18:02 ` James E Wilson
0 siblings, 0 replies; 13+ messages in thread
From: James E Wilson @ 2004-07-27 18:02 UTC (permalink / raw)
To: andre maute; +Cc: gcc-bugs
andre maute wrote:
> i already did that, see
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
Thanks. I forgot to check for that. I will add the info I have to the
bug report.
> -fininline-functions is enabled in -O3 for both gcc-3.3.3 and gcc-3.4.1
Yes, but there are some differences in implementation, and somehow this
is causing a problem in gcc-3.4.1.
> but not with gcc-3.3.3
I know, you already said that.
> Sorry that's wrong, cerr is declared at the beginning of the file and used at
> the end of the file.
I meant in the average_n functions, cerr is used in between where the
variable "a" is declared and when it is used. However, on further
review, this turns out not to matter. It doesn't matter where the cerr
uses are, only that they exist in the average_n functions.
If you ifdef out the code that writes to cerr, or stop using
-finline-functions, the problem goes away.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
2004-07-17 21:06 compile time regression, when adding cerr usage andre maute
2004-07-27 0:57 ` James E Wilson
@ 2004-12-10 22:11 ` andre maute
2004-12-10 23:10 ` Daniel Berlin
1 sibling, 1 reply; 13+ messages in thread
From: andre maute @ 2004-12-10 22:11 UTC (permalink / raw)
To: gcc-bugs
[-- Attachment #1: Type: text/plain, Size: 132 bytes --]
Once more i couldn't upload an attachment
with the bugzilla upload form, so i send it here.
I'll refer to it later.
Regards Andre
[-- Attachment #2: compiletimetest2.cc.gz --]
[-- Type: application/x-gzip, Size: 6722 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/16613] New: compile time regression, when adding cerr usage
@ 2004-07-18 10:11 andre dot maute at gmx dot de
2004-11-28 5:27 ` [Bug rtl-optimization/16613] [3.4 Regression] " lerdsuwa at gcc dot gnu dot org
` (6 more replies)
0 siblings, 7 replies; 13+ messages in thread
From: andre dot maute at gmx dot de @ 2004-07-18 10:11 UTC (permalink / raw)
To: gcc-bugs
See http://gcc.gnu.org/ml/gcc-bugs/2004-07/msg02181.html
because i didn't see how to attach a file in the bugzilla formular,
i first sent my bug to gcc-bugs.gcc.org
regards andre
--
Summary: compile time regression, when adding cerr usage
Product: gcc
Version: 3.4.1
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: c++
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
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
@ 2004-11-28 5:27 ` lerdsuwa at gcc dot gnu dot org
2004-12-01 13:39 ` ebotcazou at gcc dot gnu dot org
` (5 subsequent siblings)
6 siblings, 0 replies; 13+ messages in thread
From: lerdsuwa at gcc dot gnu dot org @ 2004-11-28 5:27 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From lerdsuwa at gcc dot gnu dot org 2004-11-28 05:27 -------
Confirmed. GCC 4.0 doesn't have this problem.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2004-11-28 05:27:39
date| |
Summary|[3.4/4.0? Regression] |[3.4 Regression] compile
|compile time regression, |time regression, when adding
|when adding cerr usage |cerr usage
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
2004-11-28 5:27 ` [Bug rtl-optimization/16613] [3.4 Regression] " lerdsuwa at gcc dot gnu dot org
@ 2004-12-01 13:39 ` ebotcazou at gcc dot gnu dot org
2004-12-10 22:36 ` andre dot maute at gmx dot de
` (4 subsequent siblings)
6 siblings, 0 replies; 13+ messages in thread
From: ebotcazou at gcc dot gnu dot org @ 2004-12-01 13:39 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-12-01 13:35 -------
Here's the time report on x86-64:
Execution times (seconds)
garbage collection : 3.72 ( 3%) usr 0.09 ( 1%) sys 4.03 ( 3%) wall
callgraph construction: 0.01 ( 0%) usr 0.00 ( 0%) sys 0.02 ( 0%) wall
cfg construction : 0.48 ( 0%) usr 0.04 ( 0%) sys 0.47 ( 0%) wall
cfg cleanup : 0.65 ( 1%) usr 0.05 ( 1%) sys 0.71 ( 1%) wall
trivially dead code : 0.68 ( 1%) usr 0.00 ( 0%) sys 0.66 ( 1%) wall
life analysis : 1.99 ( 2%) usr 0.02 ( 0%) sys 2.03 ( 2%) wall
life info update : 0.22 ( 0%) usr 0.00 ( 0%) sys 0.20 ( 0%) wall
alias analysis : 1.08 ( 1%) usr 0.04 ( 0%) sys 1.16 ( 1%) wall
register scan : 0.52 ( 0%) usr 0.00 ( 0%) sys 0.52 ( 0%) wall
rebuild jump labels : 0.26 ( 0%) usr 0.00 ( 0%) sys 0.27 ( 0%) wall
preprocessing : 0.05 ( 0%) usr 0.03 ( 0%) sys 0.77 ( 1%) wall
parser : 0.42 ( 0%) usr 0.11 ( 1%) sys 0.46 ( 0%) wall
name lookup : 0.09 ( 0%) usr 0.04 ( 0%) sys 0.19 ( 0%) wall
expand : 0.68 ( 1%) usr 0.05 ( 1%) sys 0.77 ( 1%) wall
varconst : 0.00 ( 0%) usr 0.00 ( 0%) sys 0.01 ( 0%) wall
integration : 0.91 ( 1%) usr 0.04 ( 0%) sys 0.94 ( 1%) wall
jump : 1.72 ( 1%) usr 0.07 ( 1%) sys 1.81 ( 1%) wall
CSE : 0.95 ( 1%) usr 0.00 ( 0%) sys 1.01 ( 1%) wall
global CSE : 29.65 (26%) usr 1.12 (13%) sys 30.85 (24%) wall
loop analysis : 50.84 (44%) usr 6.48 (76%) sys 59.33 (47%) wall
bypass jumps : 1.03 ( 1%) usr 0.10 ( 1%) sys 1.14 ( 1%) wall
CSE 2 : 0.38 ( 0%) usr 0.01 ( 0%) sys 0.37 ( 0%) wall
branch prediction : 7.13 ( 6%) usr 0.06 ( 1%) sys 7.25 ( 6%) wall
flow analysis : 0.08 ( 0%) usr 0.00 ( 0%) sys 0.09 ( 0%) wall
combiner : 0.76 ( 1%) usr 0.01 ( 0%) sys 0.82 ( 1%) wall
if-conversion : 0.28 ( 0%) usr 0.01 ( 0%) sys 0.27 ( 0%) wall
regmove : 0.16 ( 0%) usr 0.00 ( 0%) sys 0.15 ( 0%) wall
local alloc : 0.41 ( 0%) usr 0.00 ( 0%) sys 0.44 ( 0%) wall
global alloc : 6.34 ( 6%) usr 0.11 ( 1%) sys 6.49 ( 5%) wall
reload CSE regs : 1.19 ( 1%) usr 0.01 ( 0%) sys 1.30 ( 1%) wall
flow 2 : 0.19 ( 0%) usr 0.01 ( 0%) sys 0.19 ( 0%) wall
if-conversion 2 : 0.15 ( 0%) usr 0.00 ( 0%) sys 0.14 ( 0%) wall
peephole 2 : 0.06 ( 0%) usr 0.00 ( 0%) sys 0.08 ( 0%) wall
rename registers : 0.14 ( 0%) usr 0.00 ( 0%) sys 0.15 ( 0%) wall
scheduling 2 : 0.37 ( 0%) usr 0.00 ( 0%) sys 0.37 ( 0%) wall
machine dep reorg : 0.09 ( 0%) usr 0.01 ( 0%) sys 0.09 ( 0%) wall
reorder blocks : 0.15 ( 0%) usr 0.00 ( 0%) sys 0.16 ( 0%) wall
shorten branches : 0.10 ( 0%) usr 0.00 ( 0%) sys 0.11 ( 0%) wall
final : 0.16 ( 0%) usr 0.00 ( 0%) sys 0.26 ( 0%) wall
symout : 0.00 ( 0%) usr 0.00 ( 0%) sys 0.01 ( 0%) wall
rest of compilation : 0.58 ( 1%) usr 0.00 ( 0%) sys 0.56 ( 0%) wall
TOTAL : 114.68 8.51 126.68
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
2004-11-28 5:27 ` [Bug rtl-optimization/16613] [3.4 Regression] " lerdsuwa at gcc dot gnu dot org
2004-12-01 13:39 ` ebotcazou at gcc dot gnu dot org
@ 2004-12-10 22:36 ` andre dot maute at gmx dot de
2004-12-10 22:43 ` andre dot maute at gmx dot de
` (3 subsequent siblings)
6 siblings, 0 replies; 13+ messages in thread
From: andre dot maute at gmx dot de @ 2004-12-10 22:36 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From andre dot maute at gmx dot de 2004-12-10 22:36 -------
I don't think the compile time regression is solved in the actual g++-4.0.
I made some run time measurements with the attached file compiletimetest2.cc
on a PIII 550. The __DEBUG__ tests only enable <iostream> and some cerr lines.
> g++ -v
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/specs
Configured with: ../gcc-3.2.1/configure --prefix=/usr --enable-shared
--enable-languages=c,c++ --enable-threads=posix --with-slibdir=/lib
--enable-__cxa_atexit--enable-clocale=gnu
Thread model: posix
gcc version 3.2.1
> g++-3.3.5 -v
Reading specs from /opt/gcc-3.3.5/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/specs
Configured with: ../gcc-3.3.5/configure --prefix=/opt/gcc-3.3.5
--enable-shared--enable-languages=c,c++ --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --program-suffix=-3.3.5
--with-cpu=pentium3
Thread model: posix
gcc version 3.3.5
> g++-3.4.3 -v
Reading specs from /opt/gcc-3.4.3/lib/gcc/i686-pc-linux-gnu/3.4.3/specs
Configured with: ../gcc-3.4.3/configure --prefix=/opt/gcc-3.4.3
--enable-shared--enable-languages=c,c++ --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --program-suffix=-3.4.3
--with-arch=pentium3
Thread model: posix
gcc version 3.4.3
g++-4.0-20041205 -v
Reading specs from /opt/gcc-4.0-20041205/lib/gcc/i686-pc-linux-gnu/4.0.0/specs
Configured with: ../gcc-4.0-20041205/configure --prefix=/opt/gcc-4.0-20041205
--enable-shared --enable-languages=c,c++ --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --disable-nls
--program-suffix=-4.0-20041205 --with-arch=pentium3
Thread model: posix
gcc version 4.0.0 20041205 (experimental)
> time g++ -c -O3 -D __NDEBUG__ compiletimetest2.cc
real 0m9.957s user 0m9.910s sys 0m0.090s
> time g++ -c -O3 -D __DEBUG__ compiletimetest2.cc
real 0m13.544s user 0m13.270s sys 0m0.170s
> time g++-3.3.5 -c -O3 -D __NDEBUG__ compiletimetest2.cc
real 0m9.881s user 0m9.740s sys 0m0.130s
> time g++-3.3.5 -c -O3 -D __NDEBUG__ compiletimetest2.cc
real 0m9.881s user 0m9.740s sys 0m0.130s
> time g++-3.4.3 -c -O3 -D __NDEBUG__ compiletimetest2.cc
real 0m18.614s user 0m18.240s sys 0m0.310s
> time g++-3.4.3 -c -O3 -D __DEBUG__ compiletimetest2.cc
real 0m21.563s user 0m21.050s sys 0m0.510s
> time g++-4.0-20041205 -c -O3 -D __NDEBUG__ compiletimetest2.cc
real 0m24.983s user 0m24.740s sys 0m0.160s
> time g++-4.0-20041205 -c -O3 -D __DEBUG__ compiletimetest2.cc
real 0m31.269s user 0m30.230s sys 0m0.240s
Regards Andre
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
` (2 preceding siblings ...)
2004-12-10 22:36 ` andre dot maute at gmx dot de
@ 2004-12-10 22:43 ` andre dot maute at gmx dot de
2004-12-10 23:12 ` dberlin at gcc dot gnu dot org
` (2 subsequent siblings)
6 siblings, 0 replies; 13+ messages in thread
From: andre dot maute at gmx dot de @ 2004-12-10 22:43 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From andre dot maute at gmx dot de 2004-12-10 22:42 -------
sorry missed the following two lines
> time g++-3.3.5 -c -O3 -D __DEBUG__ compiletimetest2.cc
real 0m12.454s user 0m12.210s sys 0m0.230s
so g++-3.3.5 is really good,
and I don't hope that we will see 40 s for g++-4.1 ;-)
Regards Andre
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
` (3 preceding siblings ...)
2004-12-10 22:43 ` andre dot maute at gmx dot de
@ 2004-12-10 23:12 ` dberlin at gcc dot gnu dot org
2004-12-11 3:28 ` andre dot maute at gmx dot de
2004-12-11 8:10 ` pinskia at gcc dot gnu dot org
6 siblings, 0 replies; 13+ messages in thread
From: dberlin at gcc dot gnu dot org @ 2004-12-10 23:12 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From dberlin at gcc dot gnu dot org 2004-12-10 23:12 -------
(In reply to comment #9)
> g++-4.0-20041205 -v
> Reading specs from /opt/gcc-4.0-20041205/lib/gcc/i686-pc-linux-gnu/4.0.0/specs
> Configured with: ../gcc-4.0-20041205/configure --prefix=/opt/gcc-4.0-20041205
> --enable-shared --enable-languages=c,c++ --enable-threads=posix
> --enable-__cxa_atexit --enable-clocale=gnu --disable-nls
> --program-suffix=-4.0-20041205 --with-arch=pentium3
> Thread model: posix
> gcc version 4.0.0 20041205 (experimental)
You need to add --disable-checking to your configure flags in order to compare
against a development branch.
When release branches are made, checking gets turned off by default by
configure, but it's on in non-release branches.
The compiler is a *lot* slower with checking
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
` (4 preceding siblings ...)
2004-12-10 23:12 ` dberlin at gcc dot gnu dot org
@ 2004-12-11 3:28 ` andre dot maute at gmx dot de
2004-12-11 8:10 ` pinskia at gcc dot gnu dot org
6 siblings, 0 replies; 13+ messages in thread
From: andre dot maute at gmx dot de @ 2004-12-11 3:28 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From andre dot maute at gmx dot de 2004-12-11 03:28 -------
now with --disable-checking in the configure parameters for gcc-4.0
> g++-4.0-20041205-1-dc -v
Reading specs
from /opt/gcc-4.0-20041205-1-dc/lib/gcc/i686-pc-linux-gnu/4.0.0/specs
Configured with: ../gcc-4.0-20041205/configure
--prefix=/opt/gcc-4.0-20041205-1-dc --enable-shared --enable-languages=c,c++
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--disable-nls --program-suffix=-4.0-20041205-1-dc --with-arch=pentium3
--disable-checking
Thread model: posix
gcc version 4.0.0 20041205 (experimental)
> time g++-4.0-20041205-1-dc -c -O3 -D __NDEBUG__ compiletimetest2.cc
real 0m18.300s user 0m18.050s sys 0m0.250s
> time g++-4.0-20041205-1-dc -c -O3 -D __DEBUG__ compiletimetest2.cc
real 0m21.368s user 0m20.960s sys 0m0.440s
this looks much better but not as good as with g++-3.3.5
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
` (5 preceding siblings ...)
2004-12-11 3:28 ` andre dot maute at gmx dot de
@ 2004-12-11 8:10 ` pinskia at gcc dot gnu dot org
6 siblings, 0 replies; 13+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-12-11 8:10 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-11 08:10 -------
Here is my timings for 3.3.2 vs the mainline on powerpc-darwin (yesterdays before a patch which
should speed it up a little more):
[zhivago:~/src/localgccPRs] pinskia% time ~/gcc-3.3//bin/gcc pr16613.ii -S -D__DEBUG__ -O2
5.600u 0.340s 0:06.99 84.9% 0+0k 0+3io 0pf+0w
[zhivago:~/src/localgccPRs] pinskia% time ~/local3/bin/gcc pr16613.ii -S -D__DEBUG__ -O2
6.190u 0.590s 0:07.69 88.1% 0+0k 0+0io 0pf+0w
Plus this is a mainline preprocessed source so it looks like the mainline is slightly slower than 3.3.2
(about 10%).
For -O0:
[zhivago:~/src/localgccPRs] pinskia% time ~/gcc-3.3//bin/gcc pr16613.ii -S -D__DEBUG__
2.980u 0.260s 0:04.70 68.9% 0+0k 0+0io 0pf+0w
[zhivago:~/src/localgccPRs] pinskia% time ~/local3/bin/gcc pr16613.ii -S -D__DEBUG__
1.600u 0.270s 0:02.29 81.6% 0+0k 0+0io 0pf+0w
So we are much faster for -O0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2004-12-11 8:10 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-07-17 21:06 compile time regression, when adding cerr usage andre maute
2004-07-27 0:57 ` James E Wilson
2004-07-27 8:00 ` andre maute
2004-07-27 18:02 ` James E Wilson
2004-12-10 22:11 ` [Bug rtl-optimization/16613] [3.4 Regression] " andre maute
2004-12-10 23:10 ` Daniel Berlin
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
2004-11-28 5:27 ` [Bug rtl-optimization/16613] [3.4 Regression] " lerdsuwa at gcc dot gnu dot org
2004-12-01 13:39 ` ebotcazou at gcc dot gnu dot org
2004-12-10 22:36 ` andre dot maute at gmx dot de
2004-12-10 22:43 ` andre dot maute at gmx dot de
2004-12-10 23:12 ` dberlin at gcc dot gnu dot org
2004-12-11 3:28 ` andre dot maute at gmx dot de
2004-12-11 8:10 ` pinskia at gcc dot gnu dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).