[Bug regression/21456] compile time regression(s) after gcc-4.0-20050326, 4.0 (+300%) 4.1 (+500%)
--- Additional Comments From andre dot maute at gmx dot de 2005-07-07 23:05 --- oh well, once more the compiletime increased g++-4.1-20050604 -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.1-20050604/configure --prefix=/opt/gcc-4.1-20050604 --program-suffix=-4.1-20050604 --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 20050604 (experimental) time g++-4.1-20050604 -c -O3 -D __NDEBUG__ compiletimetest2.cc real1m34.055s user1m31.347s sys 0m1.215s time g++-4.1-20050604 -c -O3 -D __DEBUG__ compiletimetest2.cc real1m44.792s user1m42.236s sys 0m1.117s g++-4.1-20050702 -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.1-20050702/configure --prefix=/opt/gcc-4.1-20050702 --program-suffix=-4.1-20050702 --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 20050702 (experimental) time g++-4.1-20050702 -c -O3 -D __NDEBUG__ compiletimetest2.cc real2m21.944s user2m20.101s sys 0m1.146s time g++-4.1-20050702 -c -O3 -D __DEBUG__ compiletimetest2.cc real2m33.524s user2m32.146s sys 0m1.111s -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21456
[Bug regression/21456] compile time regression(s) after gcc-4.0-20050326, 4.0 (+300%) 4.1 (+500%)
--- Additional Comments From andre dot maute at gmx dot de 2005-07-08 11:17 --- (In reply to comment #3) Daniel Berlin suggested to check if -O2 compile times have increased too. indeed they DID! there is a bigger regression between 2005/03/26 and 2005/04/09 for gcc-4.0 and there is a bigger regression between 2005/06/04 and 2005/07/02 for gcc-4.1 the time reports for these four versions are at the end of this message time g++-3.3.6 -c -O2 -D __NDEBUG__ compiletimetest2.cc real0m12.330s user0m11.987s sys 0m0.238s time g++-3.3.6 -c -O2 -D __DEBUG__ compiletimetest2.cc real0m15.640s user0m14.251s sys 0m0.449s time g++-3.4.4 -c -O2 -D __NDEBUG__ compiletimetest2.cc real0m18.919s user0m18.046s sys 0m0.344s time g++-3.4.4 -c -O2 -D __DEBUG__ compiletimetest2.cc real0m21.822s user0m20.616s sys 0m0.506s time g++-4.0-20050326 -c -O2 -D __NDEBUG__ compiletimetest2.cc real0m16.376s user0m15.592s sys 0m0.259s time g++-4.0-20050326 -c -O2 -D __DEBUG__ compiletimetest2.cc real0m18.449s user0m17.506s sys 0m0.406s time g++-4.0-20050409 -c -O2 -D __NDEBUG__ compiletimetest2.cc real0m51.759s user0m50.226s sys 0m0.836s time g++-4.0-20050409 -c -O2 -D __DEBUG__ compiletimetest2.cc real0m54.810s user0m53.208s sys 0m0.837s time g++-4.0-20050602 -c -O2 -D __NDEBUG__ compiletimetest2.cc real0m51.109s user0m50.370s sys 0m0.736s time g++-4.0-20050602 -c -O2 -D __DEBUG__ compiletimetest2.cc real0m56.077s user0m53.900s sys 0m0.903s time g++-4.0-20050630 -c -O2 -D __NDEBUG__ compiletimetest2.cc real0m51.137s user0m50.382s sys 0m0.755s time g++-4.0-20050630 -c -O2 -D __DEBUG__ compiletimetest2.cc real0m55.065s user0m53.141s sys 0m0.837s time g++-4.1-20050604 -c -O2 -D __NDEBUG__ compiletimetest2.cc real0m54.375s user0m52.576s sys 0m0.840s time g++-4.1-20050604 -c -O2 -D __DEBUG__ compiletimetest2.cc real0m57.049s user0m55.780s sys 0m0.767s time g++-4.1-20050702 -c -O2 -D __NDEBUG__ compiletimetest2.cc real1m15.242s user1m13.780s sys 0m0.820s time g++-4.1-20050702 -c -O2 -D __DEBUG__ compiletimetest2.cc real1m18.751s user1m17.090s sys 0m0.885s the configure options for the various versions can be found in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21456 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613 ALL are configured with --disable-checking time g++-4.0-20050326 -c -O2 -D __NDEBUG__ compiletimetest2.cc -ftime-report Execution times (seconds) callgraph construction: 0.05 ( 0%) usr 0.00 ( 0%) sys 0.05 ( 0%) wall callgraph optimization: 0.01 ( 0%) usr 0.00 ( 0%) sys 0.01 ( 0%) wall cfg construction : 0.01 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall cfg cleanup : 0.30 ( 2%) usr 0.01 ( 1%) sys 0.34 ( 2%) wall trivially dead code : 0.13 ( 1%) usr 0.00 ( 0%) sys 0.17 ( 1%) wall life analysis : 0.45 ( 3%) usr 0.00 ( 0%) sys 0.62 ( 4%) wall life info update : 0.12 ( 1%) usr 0.01 ( 1%) sys 0.14 ( 1%) wall alias analysis: 0.25 ( 2%) usr 0.00 ( 0%) sys 0.21 ( 1%) wall register scan : 0.26 ( 2%) usr 0.00 ( 0%) sys 0.20 ( 1%) wall rebuild jump labels : 0.01 ( 0%) usr 0.00 ( 0%) sys 0.04 ( 0%) wall preprocessing : 0.07 ( 0%) usr 0.05 ( 6%) sys 0.11 ( 1%) wall parser: 0.38 ( 2%) usr 0.09 (11%) sys 0.62 ( 4%) wall name lookup : 0.11 ( 1%) usr 0.18 (21%) sys 0.11 ( 1%) wall integration : 0.27 ( 2%) usr 0.00 ( 0%) sys 0.31 ( 2%) wall tree gimplify : 0.17 ( 1%) usr 0.00 ( 0%) sys 0.20 ( 1%) wall tree eh : 0.01 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall tree CFG construction : 0.01 ( 0%) usr 0.02 ( 2%) sys 0.04 ( 0%) wall tree CFG cleanup : 0.10 ( 1%) usr 0.01 ( 1%) sys 0.14 ( 1%) wall tree find referenced vars: 0.04 ( 0%) usr 0.01 ( 1%) sys 0.04 ( 0%) wall tree PTA : 0.12 ( 1%) usr 0.01 ( 1%) sys 0.22 ( 1%) wall tree alias analysis : 0.08 ( 1%) usr 0.00 ( 0%) sys 0.11 ( 1%) wall tree PHI insertion: 0.11 ( 1%) usr 0.00 ( 0%) sys 0.13 ( 1%) wall tree SSA rewrite : 0.14 ( 1%) usr 0.01 ( 1%) sys 0.06 ( 0%) wall tree SSA other: 0.25 ( 2%) usr 0.16 (19%) sys 0.39 ( 2%) wall tree operand scan : 0.21 ( 1%) usr 0.12 (14%) sys 0.51 ( 3%) wall dominator optimization: 0.58 ( 4%) usr 0.01 ( 1%) sys 0.59 ( 4%) wall tree SRA : 0.01 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall tree CCP : 0.07 ( 0%) usr 0.00 ( 0%) sys 0.04 ( 0%) wall tree split crit edges : 0.01 ( 0%) usr 0.00 ( 0%) sys 0.01 ( 0%) wall tree PRE : 0.19 ( 1%) usr
[Bug c++/23051] New: weird include path?
Suppose you have the following bash script called memory in your current directory memory --- #/bin/sh memory --- and the following mini C++ file hello.cxx - #include hello.cxx - calling now g++ -I . hello.cxx -c the compiler will print MANY errors. it looks like it will include the local file memory Shouldn't include the shipped ? Regards Andre -- Summary: weird include path? Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal 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 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=23051
[Bug c++/23051] weird include path?
--- Additional Comments From andre dot maute at gmx dot de 2005-07-25 01:06 --- (In reply to comment #0) > the compiler will print MANY errors. > it looks like it will include the local file memory the compiler prints MANY errors. it looks like it includes the local file memory Sorry Andre -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23051
[Bug rtl-optimization/16613] [3.4/4.0 Regression] compile time regression, when adding cerr usage
--- Additional Comments From andre dot maute at gmx dot de 2005-05-01 23:42 --- i have run my compile time test again, here are the timings and something has gone worse after 2005/03/26 > g++-4.0-20050326 -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.0-20050326/configure --prefix=/opt/gcc-4.0-20050326 --program-suffix=-4.0-20050326 --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.0.0 20050326 (prerelease) > g++-4.0-20050409 -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.0-20050409/configure --prefix=/opt/gcc-4.0-20050409 --program-suffix=-4.0-20050409 --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.0.0 20050409 (prerelease) > g++-4.0-20050430 -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.0-20050430/configure --prefix=/opt/gcc-4.0-20050430 --program-suffix=-4.0-20050430 --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.0.1 20050430 (prerelease) > time g++-4.0-20050326 -c -O3 -D __NDEBUG__ compiletimetest2.cc real0m16.128suser0m15.775ssys 0m0.282s > time g++-4.0-20050326 -c -O3 -D __DEBUG__ compiletimetest2.cc real0m18.842suser0m18.326ssys 0m0.488s > time g++-4.0-20050409 -c -O3 -D __NDEBUG__ compiletimetest2.cc real0m52.158suser0m51.030ssys 0m1.012s > time g++-4.0-20050409 -c -O3 -D __DEBUG__ compiletimetest2.cc real0m55.566suser0m54.460ssys 0m0.996s > time g++-4.0-20050430 -c -O3 -D __NDEBUG__ compiletimetest2.cc real0m52.450suser0m51.277ssys 0m0.982s > time g++-4.0-20050430 -c -O3 -D __DEBUG__ compiletimetest2.cc real0m55.270suser0m54.364ssys 0m0.906s the assemply file generated with g++-4.0-20050409 is twice as large than that generated with g++-4.0-20050326 using the option "-save-temps" > g++-4.0-20050326 -c -O3 -D __NDEBUG__ compiletimetest2.cc -save-temps > ls -al compiletimetest2.cc -rw-r--r--1 login500 users 621326 May 2 01:36 compiletimetest2.s > g++-4.0-20050409 -c -O3 -D __NDEBUG__ compiletimetest2.cc -save-temps > ls -al compiletimetest2.cc -rw-r--r--1 login500 users 1186872 May 2 01:34 compiletimetest2.s > g++-4.0-20050430 -c -O3 -D __NDEBUG__ compiletimetest2.cc -save-temps > ls -al compiletimetest2.cc -rw-r--r--1 login500 users 1186872 May 2 01:37 compiletimetest2.s using -ftime-reports reveals only that nearly every optimization pass has gone worse. Regards Andre -- What|Removed |Added Summary|[3.4 Regression] compile|[3.4/4.0 Regression] compile |time regression, when adding|time regression, when adding |cerr usage |cerr usage http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
[Bug rtl-optimization/16613] [3.4/4.0 Regression] compile time regression, when adding cerr usage
--- Additional Comments From andre dot maute at gmx dot de 2005-05-05 20:12 --- i want to supplement my compile time tests which shows that a regression was introduced between 2005/03/26 an 2005/04/02 > g++-4.0-20050402 -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.0-20050402/configure --prefix=/opt/gcc-4.0-20050402 --program-suffix=-4.0-20050402 --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.0.0 20050402 (prerelease) > time g++-4.0-20050402 -c -O3 -D __NDEBUG__ compiletimetest2.cc real0m52.126suser0m51.187ssys 0m0.777s > time g++-4.0-20050402 -c -O3 -D __DEBUG__ compiletimetest2.cc real0m55.409suser0m54.280ssys 0m0.935s > g++-4.0-20050402 -c -O3 -D __NDEBUG__ compiletimetest2.cc -save-temps > ls -al compiletimetest2.s -rw-r--r--1 login500 users 1186149 May 5 22:05 compiletimetest2.s Regards Andre -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
[Bug regression/21456] New: compile time regression(s) after gcc-4.0-20050326, 4.0 (+300%) 4.1 (+500%)
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
real1m47.056suser1m45.474s sys 0m1.392s
> time g++-4.1-20050508 -c -O3 -D __DEBUG__ compiletimetest2.cc
real1m53.201suser1m51.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
[Bug c++/21924] New: namespace ignored
the following code compiles with 3.4.4, 4.0-20050430
namespace element {
struct Element {};
void connect( Element* e1, Element* e2 ) {}
} // namespace element
void foo_connect( element::Element* e1, element::Element* e2 ) {
connect(e1,e2);
}
Isn't it necessary to open the namespace in foo_connect?
--
Summary: namespace ignored
Product: gcc
Version: 4.0.1
Status: UNCONFIRMED
Severity: normal
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
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=21924
[Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
--- 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 real0m18.300suser0m18.050ssys 0m0.250s > time g++-4.0-20041205-1-dc -c -O3 -D __DEBUG__ compiletimetest2.cc real0m21.368suser0m20.960ssys 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
[Bug regression/19174] New: wrong code regression or library problem in gcc-4.0-20041226
consider the following code snippet
nan.cc ---
#include
int main() {
double x = 0.8023;
std::cout << x << " ";
std::cout << x << " ";
std::cout << std::endl;
return 0;
}
nan.cc ---
> g++-4.0-20041226 -v
Using built-in specs.
Configured with: ../gcc-4.0-20041226/configure --prefix=/opt/gcc-4.0-20041226
--enable-shared --enable-languages=c,c++ --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --disable-nls
--program-suffix=-4.0-20041226 --with-arch=pentium3 --disable-checking
Thread model: posix
gcc version 4.0.0 20041226 (experimental)
> g++-4.0-20041226 nan.cc
> ldd a.out
libstdc++.so.6 => /opt/gcc-4.0-20041226/lib/libstdc++.so.6 (0x40017000)
libm.so.6 => /lib/libm.so.6 (0x400fc000)
libgcc_s.so.1 => /opt/gcc-4.0-20041226/lib/libgcc_s.so.1 (0x4011f000)
libc.so.6 => /lib/libc.so.6 (0x40129000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
> ./a.out
0.56 nan
well this nan shouldn't be there
> g++-4.0-20041226 nan.cc -static
> ./a.out
0.56 0.56
> g++-4.0-20041212 -v
Reading specs from /opt/gcc-4.0-20041212/lib/gcc/i686-pc-linux-gnu/4.0.0/specs
Configured with: ../gcc-4.0-20041212/configure --prefix=/opt/gcc-4.0-20041212
--enable-shared --enable-languages=c,c++ --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --disable-nls
--program-suffix=-4.0-20041212 --with-arch=pentium3 --disable-checking
Thread model: posix
gcc version 4.0.0 20041212 (experimental)
> g++-4.0-20041212 nan.cc
> ldd ./a.out
libstdc++.so.6 => /opt/gcc-4.0-20041212/lib/libstdc++.so.6 (0x40017000)
libm.so.6 => /lib/libm.so.6 (0x400fb000)
libgcc_s.so.1 => /opt/gcc-4.0-20041212/lib/libgcc_s.so.1 (0x4011e000)
libc.so.6 => /lib/libc.so.6 (0x40128000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
> ./a.out
0.56 0.56
g++-4.0-20041212 doesn't have this problem
--
Summary: wrong code regression or library problem in gcc-4.0-
20041226
Product: gcc
Version: 4.0.0
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
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2004-12-28 17:21 --- Oh i forgot my system triplets, they are all i686-pc-linux-gnu g++-4.0-20041226 -v doesn't show the triplet any more, there is only a line Using built-in specs. i suggest to remove this new feature for convenience. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2004-12-28 18:03 --- it looks like it is really a library problem. Using the libraries from gcc-4.0-20041212 everything is fine, although nan.cc was nevertheless compiled with gcc-4.0-20041226. > ldd a.out libstdc++.so.6 => /opt/gcc-4.0-20041212/lib/libstdc++.so.6 (0x40017000) libm.so.6 => /lib/libm.so.6 (0x400fb000) libgcc_s.so.1 => /opt/gcc-4.0-20041212/lib/libgcc_s.so.1 (0x4011e000) libc.so.6 => /lib/libc.so.6 (0x40128000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) > ./a.out 0.56 0.56 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2004-12-29 11:14 --- Sorry no cvs available, and only a modem dial-up connection, i'll try it when the new snapshot diff is available. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2005-01-01 23:58 --- if i remove the architecture option from the configure parameters > g++-4.0-20041226-na -v Using built-in specs. Configured with: ../gcc-4.0-20041226/configure --prefix=/opt/gcc-4.0-20041226-na--enable-shared --enable-languages=c,c++ --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --disable-nls --program-suffix=-4.0-20041226-na --disable-checking Thread model: posix gcc version 4.0.0 20041226 (experimental) > g++-4.0-20041226-na nan.cc > ./a.out 0.56 0.56 > g++-4.0-20041226-na nan.cc -march=pentium3 > ./a.out 0.56 0.56 is this mysterious? because now everything looks o.k. for compilation of gcc-4.0-20041226 i used gcc-4.0-20041212. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2005-01-02 21:06 --- well i've tested gcc-4.0-20050102, (compiled with gcc-4.0-20041212) > g++-4.0-20050102 -v Using built-in specs. Configured with: ../gcc-4.0-20050102/configure --prefix=/opt/gcc-4.0-20050102 --enable-shared --enable-languages=c,c++ --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --disable-nls --program-suffix=-4.0-20050102 --with-arch=pentium3 --disable-checking Thread model: posix gcc version 4.0.0 20050102 (experimental) > g++-4.0-20050102 nan.cc > ./a.out 0.56 nan the problem is still there -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2005-01-02
23:44 ---
the C-version works with every compiler
nan.c ---
#include
int main() {
double x = 0.8023;
printf( "%f ", x );
printf( "%f ", x );
printf( "\n" );
return 0;
}
nan.c ---
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2005-01-04 17:46 --- tried gcc-4.0-20050102 with the patch http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/i386/i386.md.diff?cvsroot=gcc&r1=1.597&r2=1.598 from http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19235 and the problem still does occur :-( P.S.: compiled with gcc-4.0-20041212 -- What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2005-01-10 00:00 --- tried gcc-4.0-20050109 compile with gcc-3.4.3 the problem still appears -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2005-01-17 12:28 --- gcc-4.0-20050116 compiled with gcc-3.3.5 this time with the configure parameter: --with-arch=pentium3 fails withOUT the configure parameter: --with-arch=pentium3 everything is o.k. with respect to the library things i mentionend, is it possible that libstdc++.so is miscompiled, when the above configure parameter is used.? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
--- Additional Comments From andre dot maute at gmx dot de 2005-01-24 10:42 --- It looks like it is fixed now Compiling gcc-4.0-20050123 with a gcc-4.0-20050116, which has the architecture option disabled, works. Great! Regards Andre -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
[Bug middle-end/19583] [4.0 Regression] Incorrect diagnostic: control may reach end of non-void function '...' being inlined
--- Additional Comments From andre dot maute at gmx dot de 2005-01-24
12:27 ---
with the following the problem also does occur
-- O3Wall.cc ---
#include
double test( double x ) {
return fabs(x);
}
-- O3Wall.cc ---
> g++-4.0-20050123 O3Wall.cc -O3 -Wall -c
O3Wall.cc: In function 'double test(double)':
O3Wall.cc:4: warning: control may reach end of non-void function 'double
fabs(double)' being inlined
> g++-4.0-20050123 -v
Using built-in specs.
Configured with: ../gcc-4.0-20050123/configure --prefix=/opt/gcc-4.0-20050123
--enable-shared --enable-languages=c,c++ --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --disable-nls
--program-suffix=-4.0-20050123 --disable-checking --with-arch=pentium3
Thread model: posix
gcc version 4.0.0 20050123 (experimental)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19583
[Bug middle-end/19583] [4.0 Regression] Incorrect diagnostic: control may reach end of non-void function '...' being inlined
--- Additional Comments From andre dot maute at gmx dot de 2005-01-24 12:30 --- oh sorry, i did not read the bug history :-( regards andre -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19583
[Bug middle-end/19583] [4.0 Regression] Incorrect diagnostic: control may reach end of non-void function '...' being inlined
--- Additional Comments From andre dot maute at gmx dot de 2005-01-26
01:20 ---
(In reply to comment #11)
> Anyways patch here:
<http://gcc.gnu.org/ml/gcc-patches/2005-01/msg01675.html>.
the patch (used with gcc-4.0-20050123) doesn't fix the following code
-- O3Wall-2.cc ---
#include
int main() {
int x = 3; int* ptr = &x;
std::stack s;
s.push(ptr);
s.pop();
return 0;
}
-- O3Wall-2.cc ---
> g++-4.0-20050123-1 -O3 -Wall O3Wall-2.cc
/opt/gcc-4.0-20050123-1/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0/bits/stl_deque.h:
In destructor 'std::_Deque_base<_Tp, _Alloc>::~_Deque_base() [with _Tp = int*,
_Alloc = std::allocator]':
/opt/gcc-4.0-20050123-1/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0/bits/stl_deque.h:411:
warning: control may reach end of non-void function 'typename
_Alloc::rebind<_Tp*>::other std::_Deque_base<_Tp,
_Alloc>::_M_get_map_allocator() const [with _Tp = int*, _Alloc =
std::allocator]' being inlined
/opt/gcc-4.0-20050123-1/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0/bits/deque.tcc:
In member function 'void std::deque<_Tp, _Alloc>::_M_reallocate_map(size_t,
bool) [with _Tp = int*, _Alloc = std::allocator]':
/opt/gcc-4.0-20050123-1/lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../include/c++/4.0.0/bits/deque.tcc:750:
warning: control may reach end of non-void function '_Tp**
std::_Deque_base<_Tp, _Alloc>::_M_allocate_map(size_t) [with _Tp = int*,
_Alloc = std::allocator]' being inlined
> g++-4.0-20050123-1 -v
Using built-in specs.
Configured with: ../gcc-4.0-20050123/configure
--prefix=/opt/gcc-4.0-20050123-1 --enable-shared --enable-languages=c,c++
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--disable-nls --program-suffix=-4.0-20050123-1 --disable-checking
--with-arch=pentium3
Thread model: posix
gcc version 4.0.0 20050123 (experimental)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19583
[Bug c++/18429] New: ICE for g++-3.3.5/ endless loop for g++-3.4.3 (template and namespace)
the following code ICEs with g++-3.3.5 and freezes g++-3.4.3
--- begin of tree.cc --
namespace numbers {
int subtrees = 4;
}
template< class T >
class Tree {
public:
Tree* L[numbers::subtrees];
Tree* R[numbers::subtrees];
public:
Tree() {
L[0] = 0;
R[0] = 0;
}
~Tree() {
if( L[0] )
delete [] L[0];
if( R[0] )
delete [] R[0];
}
};
int main() {
Tree t;
return 0;
}
--- end of tree.cc
> 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
--
Summary: ICE for g++-3.3.5/ endless loop for g++-3.4.3 (template
and namespace)
Product: gcc
Version: 3.3.5
Status: UNCONFIRMED
Severity: normal
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
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=18429
[Bug c++/18904] New: 4.0-20041205 regression ICE with -O3
the following code ICEs with
g++-4.0-20041205 -c -O3 ice.cc
/*-- begin of ice.cc */
struct Data;
struct Wrapper {
Data* D;
};
inline void initValue(
Wrapper &w,
int Data::* res
) {
for( int i = 0; i < 4; i++ )
(w.D->*res) = 0;
}
struct Data {
int X;
void init( Wrapper &w ) {
w.D = this;
initValue(w, &Data::X);
}
};
int main() {
Wrapper w;
Data d;
d.init(w);
return 0;
}
/*-- end of ice.cc */
login > /opt/gcc-4.0-20041205/bin/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-threads=posix --with-system-zlib --enable-__cxa_atexit
--enable-languages=c,c++ --program-suffix=-4.0-20041205
Thread model: posix
gcc version 4.0.0 20041205 (experimental)
Regards Andre
--
Summary: 4.0-20041205 regression ICE with -O3
Product: gcc
Version: 4.0.0
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=18904
[Bug c++/18904] 4.0-20041205 regression ICE with -O3
--- Additional Comments From andre dot maute at gmx dot de 2004-12-09 15:08 --- g++-3.3.3, g++-3.4.1 and g++-3.4.3 are o.k. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18904
[Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
--- 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 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.957suser 0m9.910ssys 0m0.090s > time g++ -c -O3 -D __DEBUG__ compiletimetest2.cc real0m13.544suser0m13.270ssys 0m0.170s > time g++-3.3.5 -c -O3 -D __NDEBUG__ compiletimetest2.cc real 0m9.881suser 0m9.740ssys 0m0.130s > time g++-3.3.5 -c -O3 -D __NDEBUG__ compiletimetest2.cc real 0m9.881suser 0m9.740ssys 0m0.130s > time g++-3.4.3 -c -O3 -D __NDEBUG__ compiletimetest2.cc real0m18.614suser0m18.240ssys 0m0.310s > time g++-3.4.3 -c -O3 -D __DEBUG__ compiletimetest2.cc real0m21.563suser0m21.050ssys 0m0.510s > time g++-4.0-20041205 -c -O3 -D __NDEBUG__ compiletimetest2.cc real0m24.983suser0m24.740ssys 0m0.160s > time g++-4.0-20041205 -c -O3 -D __DEBUG__ compiletimetest2.cc real0m31.269suser0m30.230ssys 0m0.240s Regards Andre -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
[Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
--- 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 real0m12.454suser0m12.210ssys 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
