Bug#102193: gcc-3.0: compiled code with gcc 3.0 is slow and big
On Friday, January 4, 2002, at 08:17 , Morten Brix Pedersen wrote: mbp:~$ g++ benchmark.cpp ; ls -l a.out ; time a.out ; g++-3.0 benchmark.cpp ; ls -l a.out ; time a.out Well, first, take . out of your path! I get: -rwxr-xr-x1 anthony anthony 42840 Jan 5 23:46 a.out real0m7.870s user0m7.210s sys 0m0.490s -rwxr-xr-x1 anthony anthony 37976 Jan 5 23:47 a.out real0m13.835s user0m13.240s sys 0m0.420s Ouch! Turning on the optimizer does help some, though: [EMAIL PROTECTED]:morten$ g++ -O3 -march=i686 benchmark.cpp ; ls -l a.out ; time ./a.out ; g++-3.0 -O3 -march=i686 benchmark.cpp; ls -l a.out; time ./a.out -rwxr-xr-x1 anthony anthony 19173 Jan 5 23:50 a.out real0m3.146s user0m2.640s sys 0m0.470s -rwxr-xr-x1 anthony anthony 19109 Jan 5 23:51 a.out real0m4.617s user0m4.130s sys 0m0.410s [EMAIL PROTECTED]:morten$ Now only 1/3 slower. Still not good.
[¼ºÀα¤°í]1¿ù 2ÀÏ ½Å±Ô ¼ºÀλçÀÌÆ® ¿ÀÇÂÇÕ´Ï´Ù..
Bug#102193: gcc-3.0: compiled code with gcc 3.0 is slow and big
On Sat, Jan 05, 2002 at 02:17:21AM +0100, Morten Brix Pedersen wrote: > Package: gcc-3.0 > Version: 1:3.0.3-1 > > I don't know if it's valid for this bug report, but all code I have tried is > slower in g++ 3, here's a simple example: There's lots of reasons for this. The biggest one is that the conforming libstdc++ v3.0 is muchlarger and more complicated. > (numbers first, code in the bottom) > mbp:~$ g++ benchmark.cpp ; ls -l a.out ; time a.out ; g++-3.0 benchmark.cpp > ; ls -l a.out ; time a.out > -rwxr-xr-x1 mbp mbp 42840 5 jan 02:14 a.out* > > real0m13.542s > user0m6.200s > sys 0m0.220s > -rwxr-xr-x1 mbp mbp 38016 5 jan 02:14 a.out* > > real0m20.882s > user0m9.950s > sys 0m0.080s The default for G++ is, and has always been, to compile without optimization. Try with -O2 (or -Os if size is your concern) (or -O3 in some cases). It may still be slower, but probably much less so. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer
Bug#126240: marked as done (gpc: Internal compiler error: program gpc1 got fatal signal 11)
Your message dated Sat, 05 Jan 2002 14:58:16 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#126240: fixed in gcc-2.95 2.95.4.ds8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 23 Dec 2001 04:46:49 + >From [EMAIL PROTECTED] Sat Dec 22 22:46:48 2001 Return-path: <[EMAIL PROTECTED]> Received: from rzaixsrv2.rrz.uni-hamburg.de [134.100.32.71] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 16I0XA-0007nS-00; Sat, 22 Dec 2001 22:46:48 -0600 Received: from burse.uni-hamburg.de ([EMAIL PROTECTED] [134.100.252.249]) by rzaixsrv2.rrz.uni-hamburg.de (8.11.0/8.11.0) with ESMTP id fBN4kkb68106; Sun, 23 Dec 2001 05:46:46 +0100 Received: from forcix.burse.uni-hamburg.de (forcix.burse.uni-hamburg.de [192.168.42.38]) by burse.uni-hamburg.de (8.10.2/8.10.2) with ESMTP id fBN4kik13062; Sun, 23 Dec 2001 05:46:46 +0100 Received: from forcer by forcix.burse.uni-hamburg.de with local (Exim 3.33 #1 (Debian)) id 16I0X6-Uv-00; Sun, 23 Dec 2001 05:46:44 +0100 From: Jorgen Schaefer <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: gpc: Internal compiler error: program gpc1 got fatal signal 11 X-Reportbug-Version: 1.41.142 X-Mailer: reportbug 1.41.142 Date: Sun, 23 Dec 2001 05:46:44 +0100 Message-Id: <[EMAIL PROTECTED]> Sender: Jorgen Schaefer <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Package: gpc Version: 2:2.95.4-9 Severity: normal Hi there! While trying to compile the following program: http://www.snsg.org/snsg-0.4.1.pas.gz I get the error: <0>[EMAIL PROTECTED]:~$ gpc snsg-0.4.1.pas gpc: Internal compiler error: program gpc1 got fatal signal 11 A "Hello, World" program can be compiled... -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux forcix 2.4.14 #5 Tue Nov 6 23:04:54 CET 2001 i686 Locale: LANG=C, LC_CTYPE=de_DE Versions of packages gpc depends on: ii cpp2:2.95.4-9The GNU C preprocessor. ii gcc-2.95 1:2.95.4-0.011006 The GNU C compiler. ii gpc-2.95 1:2.95.4-0.011006 The GNU Pascal compiler. --- Received: (at 126240-close) by bugs.debian.org; 5 Jan 2002 20:11:33 + >From [EMAIL PROTECTED] Sat Jan 05 14:11:33 2002 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 16MxAD-0003mB-00; Sat, 05 Jan 2002 14:11:33 -0600 Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian)) id 16MwxM-0001v2-00; Sat, 05 Jan 2002 14:58:16 -0500 From: Matthias Klose <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.66 $ Subject: Bug#126240: fixed in gcc-2.95 2.95.4.ds8-1 Message-Id: <[EMAIL PROTECTED]> Sender: James Troup <[EMAIL PROTECTED]> Date: Sat, 05 Jan 2002 14:58:16 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of gcc-2.95, which has been installed in the Debian FTP archive: chill-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-1_i386.deb cpp-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-1_all.deb cpp-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-1_i386.deb g++-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-1_i386.deb g77-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/g77-2.95-doc_2.95.4-1_all.deb g77-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-1_i386.deb gcc-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/gcc-2.95-doc_2.95.4-1_all.deb gcc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-1_i386.deb gcc-2.95_2.95.4.ds8-1.diff.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8-1.diff.gz gcc-2.95_2.95.4.ds8-1.dsc to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8-1.dsc gcc-2.95_2.95.4.ds8.orig.tar.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8.orig.tar.gz gobjc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-1_i386.deb gpc-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/gpc-2.95-doc_2.95.4-1_all.deb gpc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-1_i386.deb libg++2.8.1.3-dbg_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-1_i386.deb libg++2.8.1.3-dev_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-1_i386.deb libg++2.8.1.3-glibc2.2_2.95.4-1
Bug#126316: marked as done (gcc-2.95: version 1:2.95.4-0.011223 dated 20010522 ?)
Your message dated Sat, 05 Jan 2002 14:58:16 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#126316: fixed in gcc-2.95 2.95.4.ds8-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 23 Dec 2001 23:34:46 + >From [EMAIL PROTECTED] Sun Dec 23 17:34:46 2001 Return-path: <[EMAIL PROTECTED]> Received: from rwcrmhc53.attbi.com [204.127.198.39] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 16II8k-0005gB-00; Sun, 23 Dec 2001 17:34:46 -0600 Received: from Athlon ([12.224.234.241]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <[EMAIL PROTECTED]> for <[EMAIL PROTECTED]>; Sun, 23 Dec 2001 23:34:15 + Received: from pehasys by Athlon with local (Exim 3.33 #1 (Debian)) id 16II8F-0005LH-00 for <[EMAIL PROTECTED]>; Sun, 23 Dec 2001 15:34:15 -0800 Subject: gcc-2.95: version 1:2.95.4-0.011223 dated 20010522 ? To: Debian Bug Tracking System <[EMAIL PROTECTED]> Date: Sun, 23 Dec 2001 15:34:15 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL73 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <[EMAIL PROTECTED]> From: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Package: gcc-2.95 Version: 1:2.95.4-0.011223 Severity: minimal The description says that the version of the package is from May 2001, while version suggests it's from December 2001. It would be great if the description was fixed to make it clear and explained what version of GCC the package is. Thanks, - Peter. --- Received: (at 126316-close) by bugs.debian.org; 5 Jan 2002 20:09:13 + >From [EMAIL PROTECTED] Sat Jan 05 14:09:13 2002 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 16Mx7w-0002iy-00; Sat, 05 Jan 2002 14:09:12 -0600 Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian)) id 16MwxM-0001v4-00; Sat, 05 Jan 2002 14:58:16 -0500 From: Matthias Klose <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.66 $ Subject: Bug#126316: fixed in gcc-2.95 2.95.4.ds8-1 Message-Id: <[EMAIL PROTECTED]> Sender: James Troup <[EMAIL PROTECTED]> Date: Sat, 05 Jan 2002 14:58:16 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of gcc-2.95, which has been installed in the Debian FTP archive: chill-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-1_i386.deb cpp-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-1_all.deb cpp-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-1_i386.deb g++-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-1_i386.deb g77-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/g77-2.95-doc_2.95.4-1_all.deb g77-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-1_i386.deb gcc-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/gcc-2.95-doc_2.95.4-1_all.deb gcc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-1_i386.deb gcc-2.95_2.95.4.ds8-1.diff.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8-1.diff.gz gcc-2.95_2.95.4.ds8-1.dsc to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8-1.dsc gcc-2.95_2.95.4.ds8.orig.tar.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8.orig.tar.gz gobjc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-1_i386.deb gpc-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/gpc-2.95-doc_2.95.4-1_all.deb gpc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-1_i386.deb libg++2.8.1.3-dbg_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-1_i386.deb libg++2.8.1.3-dev_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-1_i386.deb libg++2.8.1.3-glibc2.2_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-1_i386.deb libstdc++2.10-dbg_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-1_i386.deb libstdc++2.10-dev_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dev_2.95.4-1_i386.deb libstdc++2.10-glibc2.2_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-1_i386.deb protoize-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/protoize-2.95_2.95.4-1_i386.deb A summary of the changes between this version and the previous one is attached. T
gcc-2.95_2.95.4.ds8-1_powerpc.changes INSTALLED
Installing: chill-2.95_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-1_powerpc.deb cpp-2.95_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-1_powerpc.deb g++-2.95_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-1_powerpc.deb g77-2.95_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-1_powerpc.deb gcc-2.95-nof_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/gcc-2.95-nof_2.95.4-1_powerpc.deb gcc-2.95_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-1_powerpc.deb gobjc-2.95_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-1_powerpc.deb gpc-2.95_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-1_powerpc.deb libg++2.8.1.3-dbg_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-1_powerpc.deb libg++2.8.1.3-dev_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-1_powerpc.deb libg++2.8.1.3-glibc2.2_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-1_powerpc.deb libstdc++2.10-dbg_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-1_powerpc.deb libstdc++2.10-dev_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/libstdc++2.10-dev_2.95.4-1_powerpc.deb libstdc++2.10-glibc2.2_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-1_powerpc.deb protoize-2.95_2.95.4-1_powerpc.deb to pool/main/g/gcc-2.95/protoize-2.95_2.95.4-1_powerpc.deb Thank you for your contribution to Debian.
gcc-2.95_2.95.4.ds8-1_sparc.changes INSTALLED
Installing: chill-2.95_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-1_sparc.deb cpp-2.95_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-1_sparc.deb g++-2.95_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-1_sparc.deb g77-2.95_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-1_sparc.deb gcc-2.95_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-1_sparc.deb gobjc-2.95_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-1_sparc.deb gpc-2.95_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-1_sparc.deb libg++2.8.1.3-dbg_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-1_sparc.deb libg++2.8.1.3-dev_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-1_sparc.deb libg++2.8.1.3-glibc2.2_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-1_sparc.deb libstdc++2.10-dbg_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-1_sparc.deb libstdc++2.10-dev_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/libstdc++2.10-dev_2.95.4-1_sparc.deb libstdc++2.10-glibc2.2_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-1_sparc.deb protoize-2.95_2.95.4-1_sparc.deb to pool/main/g/gcc-2.95/protoize-2.95_2.95.4-1_sparc.deb Thank you for your contribution to Debian.
gcc-2.95_2.95.4.ds8-1_i386.changes INSTALLED
Installing: chill-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-1_i386.deb cpp-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-1_all.deb cpp-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-1_i386.deb g++-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-1_i386.deb g77-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/g77-2.95-doc_2.95.4-1_all.deb g77-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-1_i386.deb gcc-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/gcc-2.95-doc_2.95.4-1_all.deb gcc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-1_i386.deb gcc-2.95_2.95.4.ds8-1.diff.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8-1.diff.gz gcc-2.95_2.95.4.ds8-1.dsc to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8-1.dsc gcc-2.95_2.95.4.ds8.orig.tar.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds8.orig.tar.gz gobjc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-1_i386.deb gpc-2.95-doc_2.95.4-1_all.deb to pool/main/g/gcc-2.95/gpc-2.95-doc_2.95.4-1_all.deb gpc-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-1_i386.deb libg++2.8.1.3-dbg_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-1_i386.deb libg++2.8.1.3-dev_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-1_i386.deb libg++2.8.1.3-glibc2.2_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-1_i386.deb libstdc++2.10-dbg_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-1_i386.deb libstdc++2.10-dev_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dev_2.95.4-1_i386.deb libstdc++2.10-glibc2.2_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-1_i386.deb protoize-2.95_2.95.4-1_i386.deb to pool/main/g/gcc-2.95/protoize-2.95_2.95.4-1_i386.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 126240 126316 Thank you for your contribution to Debian.
Bug#127783: acknowledged by developer (Re: Bug#127783: gcc-3.0-source: java selftest fail)
[EMAIL PROTECTED] (Debian Bug Tracking System) writes: > This is an automatic notification regarding your Bug report > #127783: gcc-3.0-source: java selftest fail, > which was filed against the gcc-3.0 package. > > It has been closed by one of the developers, namely > Matthias Klose <[EMAIL PROTECTED]>. > > Their explanation is attached below. If this explanation is > unsatisfactory and you have not received a better one in a separate > message then please contact the developer, by replying to this email. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) > > Received: (at 127783-done) by bugs.debian.org; 5 Jan 2002 02:13:25 + > >From [EMAIL PROTECTED] Fri Jan 04 20:13:25 2002 > Return-path: <[EMAIL PROTECTED]> > Received: from mail.cs.tu-berlin.de [130.149.17.13] (root) > by master.debian.org with esmtp (Exim 3.12 1 (Debian)) > id 16MgKq-0002aW-00; Fri, 04 Jan 2002 20:13:24 -0600 > Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1]) > by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id DAA05290; > Sat, 5 Jan 2002 03:10:21 +0100 (MET) > Received: (from [EMAIL PROTECTED]) > by bolero.cs.tu-berlin.de (8.10.2+Sun/8.9.3) id g052ALe25556; > Sat, 5 Jan 2002 03:10:21 +0100 (MET) > From: Matthias Klose <[EMAIL PROTECTED]> > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > Message-ID: <[EMAIL PROTECTED]> > Date: Sat, 5 Jan 2002 03:10:20 +0100 > To: Goswin Brederlow <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > CC: Roman Zippel <[EMAIL PROTECTED]> > Subject: Re: Bug#127783: gcc-3.0-source: java selftest fail > In-Reply-To: <[EMAIL PROTECTED]> > References: <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> > X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid > Delivered-To: [EMAIL PROTECTED] > > Goswin Brederlow writes: > > Matthias Klose <[EMAIL PROTECTED]> writes: > > > > > Goswin Brederlow writes: > > > > Package: gcc-3.0 > > > > Version: 1:3.0.3-1 > > > > Severity: normal > > > > > > > > The package doesn't pass its selftests and _should_fail_ to build. > > > > It should fail when the first make fails and not continue with other > > > > selftest, otherwise errors get overlocked. > > > > > > huh? then we'll never have a build which succeeds ... > > > > Some test are expected to fail, thats fine. I hope the expected > > failures don't make the make return with an error too. > > > > But an unexpected failure suggests a new error. That should fail and > > stop the build. > > fine, if you want this behaviour on m68k, I'll do it. What do we gain? > Roman Zippel submitted the patches to build gcj on m68k, so you may > want to ask him for the failures. > > > > you deleted the interesting part. where/why doesn't it continue? > > > > It does. I think the next one was the gcc tests. That shouldn't be > > caried out since the libjava tests failed (unexpectedly). > > so all is ok. regressions on architecutures, which aren't "supported" > upstream in 3.0 (Debian has it's own patches for m68k, hppa and > sparc64) are fairly common. Sure, we can just disbale running the > testsuite. This was all on i386, m68k is still building (and looks way way worse). I would think that at least on i386 the selftest results should be as expected. Its not only gcj that has unexpected failures, its just the first. gcc and g++ also have unexpected failures and unexpected successes (which probably are ok). Can you run the testsuite with the compiled debs or does it need to be in place in the sources? If the first disabling them might be a good idea. They just take way to much time and thats just waste if noone cares about them anyway. Eigther we care about the testresults, then the build should fail if they fail, or we should not care and then not do them. I'm for failing, because those tests are a good thing. What architectures are officially supported upstream in 3.0? MfG Goswin
Bug#127928: chill-2.95: s/ 1 / Chill /g in the package description...
Package: chill-2.95 Version: 1:2.95.4-0.011223 Severity: normal Package: chill-2.95 ... Version: 1:2.95.4-0.011223 ... Description: The GNU 1 compiler. NOTE: This is not a final release, but taken from the CVS gcc-2_95-branch (dated 20010522). . This is the ITU 1 compiler. 1 is ... It seems to be clear that a s/ 1 / Chill /g is needed...
Bug#127890: gcc-3.0: ICE in gen_subprogram_die 9463
Package: gcc-3.0
Version: 1:3.0.2-4
Severity: normal
The following program bombs out on alpha:
$ gcc-3.0 -g -O2 -c a.c
a.c: In function `make_rate':
a.c:16: Internal compiler error in gen_subprogram_die, at dwarf2out.c:9463
Please submit a full bug report,
with preprocessed source if appropriate.
See http://www.gnu.org/software/gcc/bugs.html> for instructions.
It was abstracted out from drivers/atm/horizon.c in linux 2.4.17.
I've reproduced it with today's CVS gcc 3.0 branch. However, it is fixed in
the 3.1 dev branch.
-- System Information
Debian Release: 3.0
Kernel Version: Linux gondolin 2.4.17-686-smp #2 SMP Sat Dec 22 22:00:42 EST
2001 i686 unknown
Versions of the packages gcc-3.0 depends on:
ii binutils 2.11.92.0.12.3 The GNU assembler, linker and binary utiliti
ii cpp-3.03.0.2-4The GNU C preprocessor.
ii gcc-3.0-base 3.0.2-4The GNU Compiler Collection (base package).
ii libc6 2.2.4-7GNU C Library: Shared libraries and Timezone
ii libgcc13.0.2-4GCC support library.
--
int g(void);
static int make_rate(unsigned c, unsigned actual) {
unsigned br = g() ? 500 : 400;
int set_cr(void) {
actual = br;
return 0;
}
if (!c) {
return 0;
}
return set_cr();
}
Re: URGENT: Re: report #126993
On Sat, 5 Jan 2002, Matthias Klose wrote: > > > This seems to be a Debian related problem, so what do we want to do? > > > > If I build you a chroot with an older libc6/libc6-dev, can you try a > > build there? > > I doubt it: http://gcc.gnu.org/ml/gcc/2001-12/msg00868.html > > but will try... > > btw, the executables are still on vore in > ~doko/3.0.2/gcc-3.0-3.0.2ds4/build/gcc/testsuite Same thing happened on my sparc, even with my latest and without binutils-multiarch installed. Can someone take another look at the sparc patch in binutils again to make sure that it's still valid? I get the gist of it, but am not familiar enough with the 32/64 issues on ultrasparc to say whether it still does the correct thing anymore (esp in relation to what the dynamic linker expects). C
Bug#127939: gcc: ICE while compiling 2.2.19 kernel
Package: gcc Version: 1:2.95.2-13 Severity: normal I first compiled kernel (debian way) and succesfully installed it. I had to recompile it right away because wrong processor type selection. I made 'make menuconfig', changed processor type, made 'make-kpkg clean' and then 'make-kpkg --revision=tavi.1.1 kernel_image' and went to sauna. When I got back it had encountered internal compiler error while compiling namei.c (ext2). There was exactly the following -- namei.c: In function `ext2_mkdir': namei.c:538: Internal compiler error in `gen_rtx_combine' at combine.c:9328 -- and then 'make' leaving directories. When I made 'make-kpkg clean' and 'make-kpkg --revision=tavi.1.1 kernel_image' again, it worked with flying colours. Might be hardware-related.. dunno. -- kernel configuration -- # # Automatically generated make config: don't edit # CONFIG_X86=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set CONFIG_M586=y # CONFIG_M586TSC is not set # CONFIG_M686 is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_1GB=y # CONFIG_2GB is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_SMP is not set # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # General setup # CONFIG_NET=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_QUIRKS=y # CONFIG_PCI_OPTIMIZE is not set CONFIG_PCI_OLD_PROC=y # CONFIG_MCA is not set # CONFIG_VISWS is not set CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_BINFMT_JAVA is not set CONFIG_PARPORT=m CONFIG_PARPORT_PC=m # CONFIG_PARPORT_OTHER is not set # CONFIG_APM is not set # CONFIG_TOSHIBA is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set CONFIG_BLK_DEV_CMD640=y # CONFIG_BLK_DEV_CMD640_ENHANCED is not set CONFIG_BLK_DEV_RZ1000=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_VIA82C586 is not set # CONFIG_BLK_DEV_CMD646 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_IDE_CHIPSETS is not set # # Additional Block Devices # CONFIG_BLK_DEV_LOOP=m # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_PARIDE_PARPORT=m # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_HD is not set # # Networking options # CONFIG_PACKET=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_FIREWALL=y # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set CONFIG_IP_FIREWALL=y CONFIG_IP_FIREWALL_NETLINK=y CONFIG_NETLINK_DEV=y CONFIG_IP_TRANSPARENT_PROXY=y CONFIG_IP_MASQUERADE=y # # Protocol-specific masquerading support will be built as modules. # CONFIG_IP_MASQUERADE_ICMP=y # # Protocol-specific masquerading support will be built as modules. # CONFIG_IP_MASQUERADE_MOD=y CONFIG_IP_MASQUERADE_IPAUTOFW=m CONFIG_IP_MASQUERADE_IPPORTFW=m CONFIG_IP_MASQUERADE_MFW=m CONFIG_IP_ROUTER=y # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_ALIAS is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # # (it is safe to leave these untouched) # # CONFIG_INET_RARP is not set CONFIG_SKB_LARGE=y # CONFIG_IPV6 is not set # # # # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_BRIDGE is not set # CONFIG_NET_DIVERT is not set # CONFIG_LLC is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_FASTROUTE is not set # CONFIG_NET_HW_FLOWCONTROL is not set # CONFIG_CPU_IS_SLOW is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # Telephony Support # # CONFIG_PHONE is not set # CONFIG_PHONE_IXJ is not set # # SCSI support # # CONFIG_SCSI is not set # # I2O device support # # CONFIG_I2O is not set # CONFIG_I2O_PCI is not set # CONFIG_I2O_BLOCK is not set # CONFIG_I2O_SCSI is not set # # Network device support # CONFIG_NETDEVICES=y # # ARCnet devices # #
gcc-2.95_2.95.4.ds8-1_m68k.changes INSTALLED
Installing: chill-2.95_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-1_m68k.deb cpp-2.95_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-1_m68k.deb g++-2.95_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-1_m68k.deb g77-2.95_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-1_m68k.deb gcc-2.95_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-1_m68k.deb gobjc-2.95_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-1_m68k.deb gpc-2.95_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-1_m68k.deb libg++2.8.1.3-dbg_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-1_m68k.deb libg++2.8.1.3-dev_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-1_m68k.deb libg++2.8.1.3-glibc2.2_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-1_m68k.deb libstdc++2.10-dbg_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-1_m68k.deb libstdc++2.10-dev_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/libstdc++2.10-dev_2.95.4-1_m68k.deb libstdc++2.10-glibc2.2_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-1_m68k.deb protoize-2.95_2.95.4-1_m68k.deb to pool/main/g/gcc-2.95/protoize-2.95_2.95.4-1_m68k.deb Thank you for your contribution to Debian.
Bug#128026: libstdc++3: std::wcout does not perform encoding conversions
Package: libstdc++3
Version: 1:3.0.3-1
Severity: normal
Running the program
#include
int main(){
std::locale loc("de_DE.UTF-8");
std::locale::global(loc);
std::wcout<
Re: Bug#119844: gcc: __WORDSIZE definition missing
On Tue, Nov 27, 2001 at 07:22:05PM -0500, Christopher C. Chimelis wrote: > > On Tue, 27 Nov 2001, John R. Daily wrote: > > > I haven't seen any reponse from Ben, so I'm going to go ahead and > > move the bug to glibc. It would be rather unfortunate if this > > isn't fixed for woody, but at this point that may be impossible. > > Ok. I'll work it out with him when he gets back from vacation (I'm > looking after his packages anyway while he's gone). It should be fairly > easy for him to catch up (if he hasn't read the thread already). __WORDSIZE is defined in /usr/include/bits/wordsize.h, which gets included by: /usr/include/fpu_control.h /usr/include/limits.h /usr/include/stdint.h _and_ /usr/include/bits/elfclass.h /usr/include/bits/environments.h /usr/include/bits/fcntl.h /usr/include/bits/fenv.h /usr/include/bits/huge_val.h /usr/include/bits/ipc.h /usr/include/bits/mathdef.h /usr/include/bits/mathinline.h /usr/include/bits/msq.h /usr/include/bits/sem.h /usr/include/bits/setjmp.h /usr/include/bits/shm.h /usr/include/bits/sigcontext.h /usr/include/bits/siginfo.h /usr/include/bits/syscall.h /usr/include/bits/types.h /usr/include/bits/xopen_lim.h /usr/include/sys/procfs.h /usr/include/sys/ptrace.h /usr/include/sys/sysmacros.h /usr/include/sys/ucontext.h -- .--===-=-==-=---==-=-. / Ben Collins--Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
gcc-3.0_3.0.3ds3-1_m68k.changes INSTALLED
Installing: cpp-3.0_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/cpp-3.0_3.0.3-1_m68k.deb fastjar_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/fastjar_3.0.3-1_m68k.deb fixincludes_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/fixincludes_3.0.3-1_m68k.deb g++-3.0_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/g++-3.0_3.0.3-1_m68k.deb g77-3.0_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/g77-3.0_3.0.3-1_m68k.deb gcc-3.0_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/gcc-3.0_3.0.3-1_m68k.deb gcj-3.0_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/gcj-3.0_3.0.3-1_m68k.deb gobjc-3.0_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/gobjc-3.0_3.0.3-1_m68k.deb libffi2-dev_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libffi2-dev_3.0.3-1_m68k.deb libffi2_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libffi2_3.0.3-1_m68k.deb libgcc1_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libgcc1_3.0.3-1_m68k.deb libgcj2-dev_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libgcj2-dev_3.0.3-1_m68k.deb libgcj2_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libgcj2_3.0.3-1_m68k.deb libobjc1_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libobjc1_3.0.3-1_m68k.deb libstdc++3-dbg_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libstdc++3-dbg_3.0.3-1_m68k.deb libstdc++3-dev_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libstdc++3-dev_3.0.3-1_m68k.deb libstdc++3_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/libstdc++3_3.0.3-1_m68k.deb protoize_3.0.3-1_m68k.deb to pool/main/g/gcc-3.0/protoize_3.0.3-1_m68k.deb Thank you for your contribution to Debian.
Re: Bug#102193: gcc-3.0: compiled code with gcc 3.0 is slow and big
Hi,
Morten Brix Pedersen wrote:
> int main()
> {
> string test = "IUHASISAHDNI";
>
> vector vec;
> for (int i = 0; i <= 50; ++i) {
> string newstr;
> test += "NAWNASDKJNKNN";
> newstr = test;
String assignments are threadsafe now with gcc-3.0, so that will have an
additional overhead.
As already mentioned it's very important to enable optimization for c++
code.
bye, Roman
