Results for 3.3 20030222 (prerelease) testsuite on m68k-unknown-linux-gnu
LAST_UPDATED: Sat Feb 22 05:29:16 UTC 2003 Native configuration is m68k-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/bprob/g++-bprob-1.C execution,-g -fprofile-arcs UNRESOLVED: g++.dg/bprob/g++-bprob-1.C compilation, -g -fbranch-probabilities UNRESOLVED: g++.dg/bprob/g++-bprob-1.C execution,-g -fbranch-probabilities FAIL: g++.dg/bprob/g++-bprob-1.C execution,-O0 -fprofile-arcs UNRESOLVED: g++.dg/bprob/g++-bprob-1.C compilation, -O0 -fbranch-probabilities UNRESOLVED: g++.dg/bprob/g++-bprob-1.C execution,-O0 -fbranch-probabilities FAIL: g++.dg/bprob/g++-bprob-1.C execution,-O1 -fprofile-arcs UNRESOLVED: g++.dg/bprob/g++-bprob-1.C compilation, -O1 -fbranch-probabilities UNRESOLVED: g++.dg/bprob/g++-bprob-1.C execution,-O1 -fbranch-probabilities FAIL: g++.dg/bprob/g++-bprob-1.C execution,-O2 -fprofile-arcs UNRESOLVED: g++.dg/bprob/g++-bprob-1.C compilation, -O2 -fbranch-probabilities UNRESOLVED: g++.dg/bprob/g++-bprob-1.C execution,-O2 -fbranch-probabilities FAIL: g++.dg/bprob/g++-bprob-1.C execution,-O3 -fprofile-arcs UNRESOLVED: g++.dg/bprob/g++-bprob-1.C compilation, -O3 -fbranch-probabilities UNRESOLVED: g++.dg/bprob/g++-bprob-1.C execution,-O3 -fbranch-probabilities FAIL: g++.dg/bprob/g++-bprob-1.C execution,-O3 -g -fprofile-arcs UNRESOLVED: g++.dg/bprob/g++-bprob-1.C compilation, -O3 -g -fbranch-probabilities UNRESOLVED: g++.dg/bprob/g++-bprob-1.C execution,-O3 -g -fbranch-probabilities FAIL: g++.dg/bprob/g++-bprob-1.C execution,-Os -fprofile-arcs UNRESOLVED: g++.dg/bprob/g++-bprob-1.C compilation, -Os -fbranch-probabilities UNRESOLVED: g++.dg/bprob/g++-bprob-1.C execution,-Os -fbranch-probabilities FAIL: g++.dg/compat/break/bitfield7 y_tst.o compile UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o execute FAIL: g++.dg/abi/bitfield4.C execution test FAIL: g++.dg/abi/empty6.C (test for warnings, line 6) FAIL: g++.dg/warn/Wunused-2.C (test for warnings, line 5) FAIL: g++.dg/gcov/gcov-1.C execution test FAIL: 33:is #:should be 1 FAIL: 39:is #:should be 1 FAIL: 41:is #:should be 1 FAIL: 55:is #:should be 3 FAIL: 58:is #:should be 9 FAIL: 59:is #:should be 3 FAIL: 66:is #:should be 6 FAIL: 73:is #:should be 81 FAIL: 74:is #:should be 6 FAIL: 100:is #:should be 2 FAIL: 102:is #:should be 1 FAIL: 103:is #:should be 1 FAIL: 105:is #:should be 1 FAIL: 113:is #:should be 15 FAIL: 115:is #:should be 14 FAIL: 116:is #:should be 1 FAIL: 118:is #:should be 1 FAIL: 141:is #:should be 5 FAIL: 143:is #:should be 3 FAIL: 145:is #:should be 3 FAIL: 150:is #:should be 2 FAIL: 152:is #:should be 1 FAIL: 154:is #:should be 1 FAIL: 156:is #:should be 5 FAIL: 158:is #:should be 1 FAIL: 160:is #:should be 5 FAIL: 162:is #:should be 1 FAIL: 164:is #:should be 1 FAIL: 165:is #:should be 5 FAIL: 173:is #:should be 6 FAIL: 175:is #:should be 1 FAIL: 177:is #:should be 6 FAIL: 181:is #:should be 6 FAIL: 183:is #:should be 3 FAIL: 185:is #:should be 6 FAIL: 187:is #:should be 2 FAIL: 189:is #:should be 4 FAIL: 192:is #:should be 4 FAIL: 200:is #:should be 11 FAIL: 202:is #:should be 1 FAIL: 204:is #:should be 11 FAIL: 206:is #:should be 5 FAIL: 208:is #:should be 2 FAIL: 210:is #:should be 1 FAIL: 212:is #:should be 11 FAIL: 214:is #:should be 3 FAIL: 215:is #:should be 11 FAIL: 254:is #:should be 5 FAIL: 257:is #:should be 5 FAIL: 261:is #:should be 1 FAIL: 269:is #:should be 3 FAIL: 271:is #:should be 1 FAIL: 272:is #:should be 2 FAIL: 275:is #:should be 1 FAIL: 276:is #:should be 1 FAIL: 279:is #:should be 4 FAIL: 57: expected branch percentages not found: 25 FAIL: 68: expected branch percentages not found: 30 FAIL: 70: expected branch percentages not found: 32 FAIL: 72: expected branch percentages not found: 27 FAIL: 101: expected branch percentages not found: 50 FAIL: 114: expected branch percentages not found: 7 FAIL: 142: expected branch percentages not found: 40 FAIL: 144: expected branch percentages not found: 0 FAIL: 151: expected branch percentages not found: 50 FAIL: 157: expected branch percentages not found: 20 FAIL: 161: expected branch percentages not found: 20 FAIL: 163: expected branch percentages not found: 0 FAIL: 174: expected branch percentages not found: 17 FAIL: 178: expected branch percentages not found: 0 FAIL: 182: expected branch percentages not found: 50 FAIL: 186: expected branch percentages not found: 33 FAIL: 190: expected branch percentages not found: 0 FAIL: 201: expected branch percentages not found: 27 50 25 FAIL: 205: expected branch percentages not found: 45 FAIL: 207: expected branch percentages not found: 40 FAIL: 209: expected branch percentages not found: 50 FAIL: 213: ex
gcc-2.95 override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): cpp-2.95_2.95.4-16_i386.deb: package says priority is standard, override says optional. libstdc++2.10-dev_2.95.4-16_i386.deb: package says priority is standard, override says optional. gcc-2.95_2.95.4-16_i386.deb: package says priority is standard, override says optional. g++-2.95_2.95.4-16_i386.deb: package says priority is standard, override says optional. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED])
gcc-2.95_2.95.4.ds14-16_i386.changes ACCEPTED
Accepted: chill-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-16_i386.deb cpp-2.95-doc_2.95.4-16_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-16_all.deb cpp-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-16_i386.deb g++-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-16_i386.deb g77-2.95-doc_2.95.4-16_all.deb to pool/main/g/gcc-2.95/g77-2.95-doc_2.95.4-16_all.deb g77-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-16_i386.deb gcc-2.95-doc_2.95.4-16_all.deb to pool/main/g/gcc-2.95/gcc-2.95-doc_2.95.4-16_all.deb gcc-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-16_i386.deb gcc-2.95_2.95.4.ds14-16.diff.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds14-16.diff.gz gcc-2.95_2.95.4.ds14-16.dsc to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds14-16.dsc gobjc-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-16_i386.deb gpc-2.95-doc_2.95.4-16_all.deb to pool/main/g/gcc-2.95/gpc-2.95-doc_2.95.4-16_all.deb gpc-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-16_i386.deb libg++2.8.1.3-dbg_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-16_i386.deb libg++2.8.1.3-dev_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-16_i386.deb libg++2.8.1.3-glibc2.2_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-16_i386.deb libstdc++2.10-dbg_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-16_i386.deb libstdc++2.10-dev_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dev_2.95.4-16_i386.deb libstdc++2.10-glibc2.2_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-glibc2.2_2.95.4-16_i386.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 179511 Thank you for your contribution to Debian.
Bug#179511: marked as done (gpc: /usr/bin/gpc-run is a dangling symlink)
Your message dated Thu, 27 Feb 2003 02:02:28 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#179511: fixed in gcc-2.95 2.95.4.ds14-16 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; 2 Feb 2003 20:48:07 + >From [EMAIL PROTECTED] Sun Feb 02 14:48:06 2003 Return-path: <[EMAIL PROTECTED]> Received: from agrenoble-102-1-5-138.abo.wanadoo.fr (jophur) [80.15.12.138] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18fR26-0005hb-00; Sun, 02 Feb 2003 14:48:06 -0600 Received: from laurent by jophur with local (Exim 3.36 #1 (Debian)) id 18fR24-0003MO-00; Sun, 02 Feb 2003 21:48:04 +0100 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Laurent Bonnaud <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: gpc: /usr/bin/gpc-run is a dangling symlink X-Mailer: reportbug 2.10 Date: Sun, 02 Feb 2003 21:48:03 +0100 Message-Id: <[EMAIL PROTECTED]> Sender: Laurent Bonnaud <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=0.6 required=5.0 tests=SPAM_PHRASE_00_01 version=2.41 X-Spam-Level: Package: gpc Version: 1:2.95.4-15 Severity: normal Hi, this symlink is dangling: /usr/bin/gpc-run -> gpc-run-2.95 package gpc-2.95 contains /usr/bin/gpc-2.95 but not /usr/bin/gpc-run-2.95 -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux jophur 2.4.20-686 #1 Mon Jan 13 22:22:30 EST 2003 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages gpc-2.95 depends on: ii gcc-2.95 1:2.95.4-15 The GNU C compiler. ii gpc 3:2.95.4-18 The GNU Pascal compiler. ii libc62.3.1-10GNU C Library: Shared libraries an -- no debconf information --- Received: (at 179511-close) by bugs.debian.org; 27 Feb 2003 07:08:06 + >From [EMAIL PROTECTED] Thu Feb 27 01:08:04 2003 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 18oI9E-0003WJ-00; Thu, 27 Feb 2003 01:08:04 -0600 Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian)) id 18oI3o-0004oO-00; Thu, 27 Feb 2003 02:02:28 -0500 From: Matthias Klose <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.32 $ Subject: Bug#179511: fixed in gcc-2.95 2.95.4.ds14-16 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Thu, 27 Feb 2003 02:02:28 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of gcc-2.95, which is due to be installed in the Debian FTP archive: chill-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-16_i386.deb cpp-2.95-doc_2.95.4-16_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-16_all.deb cpp-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-16_i386.deb g++-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/g++-2.95_2.95.4-16_i386.deb g77-2.95-doc_2.95.4-16_all.deb to pool/main/g/gcc-2.95/g77-2.95-doc_2.95.4-16_all.deb g77-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/g77-2.95_2.95.4-16_i386.deb gcc-2.95-doc_2.95.4-16_all.deb to pool/main/g/gcc-2.95/gcc-2.95-doc_2.95.4-16_all.deb gcc-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/gcc-2.95_2.95.4-16_i386.deb gcc-2.95_2.95.4.ds14-16.diff.gz to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds14-16.diff.gz gcc-2.95_2.95.4.ds14-16.dsc to pool/main/g/gcc-2.95/gcc-2.95_2.95.4.ds14-16.dsc gobjc-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-16_i386.deb gpc-2.95-doc_2.95.4-16_all.deb to pool/main/g/gcc-2.95/gpc-2.95-doc_2.95.4-16_all.deb gpc-2.95_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-16_i386.deb libg++2.8.1.3-dbg_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dbg_2.95.4-16_i386.deb libg++2.8.1.3-dev_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-16_i386.deb libg++2.8.1.3-glibc2.2_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-glibc2.2_2.95.4-16_i386.deb libstdc++2.10-dbg_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dbg_2.95.4-16_i386.deb libstdc++2.10-dev_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libstdc++2.10-dev_2.95.4-16_i386.deb libstdc++2.10-glibc2.2_2.95.4-16_i386.deb to pool/main/g/gcc-2.95/libstdc++2.1
Bug#182795: gcc-3.2: mpqc build fails on MIPS with 'Branch out of range' error
Package: gcc-3.2 Version: 1:3.2.3-0pre2 Severity: normal Hi, compiling mpqc on MIPS results in this error: /usr/bin/gcc-3.2 -DHAVE_CONFIG_H -D_REENTRANT -I../../../../../src/lib -I/build/buildd/mpqc-2.1.3/include -I/build/buildd/mpqc-2.1.3/src/lib -O0 -Wall -c /build/buildd/mpqc-2.1.3/src/lib/chemistry/qc/dft/lebedev.c -o lebedev.o /tmp/ccIsYgSV.s: Assembler messages: /tmp/ccIsYgSV.s:361: Error: Branch out of range /tmp/ccIsYgSV.s:366: Error: Branch out of range [...] /tmp/ccIsYgSV.s:19541: Error: Branch out of range /tmp/ccIsYgSV.s:22425: Error: Branch out of range make[6]: *** [lebedev.o] Error 1 make[6]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry/qc/dft' make[5]: *** [default] Error 1 make[5]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry/qc' make[4]: *** [default] Error 1 make[4]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry' make[3]: *** [default] Error 1 make[3]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib' make[2]: *** [default] Error 1 make[2]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src' make[1]: *** [default] Error 1 make[1]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static' make: *** [build-static-stamp] Error 2 see http://buildd.debian.org/fetch.php?&pkg=mpqc&ver=2.1.3-2&arch=mipsel&; \ stamp=104604&file=log&as=raw for the full buildd log. This error also occured on gcc-2.95, I did not file it earlier because I was hoping that it might be gone in gcc-3.2. The first builds in early 2002 were done with -O and then with -O0 afterwards. You can get the source file at http://people.debian.org/~mbanck/lebedev.c thanks, Michael
Bug#180486: gcc-3.2: miscompilation on powerpc with -O2 or higher
Greetings! Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > On Mon, Feb 24, 2003 at 10:14:03AM -0500, Camm Maguire wrote: > > Greetings! > > > > Matthias Klose <[EMAIL PROTECTED]> writes: > > > > > Camm Maguire writes: > > > > Package: gcc-3.2 > > > > Version: 1:3.2.2-1 > > > > Severity: normal > > > > > > > > When compiling GCL, the produced lisp image segfaults early on > > > > iwhen using -O2 or higher. All is fine with -O, or with full > > > > optimization using earlier gcc versions on this platform. > > > > > > - did GCL compile correctly with gcc-3.0 and/or gcc-2.95 using -O2? > > > > 2.95 yes, actually even with -O3 -fomit-frame-pointer > > 3.0 don't know. > > > > > - does GCL compile correctly with gcc-snapshot using -O2? > > > > > > > Don't know, but will try it if I get a chance. I used to be able to > > try different compilers on Debian project machines relatively easily > > by: > > Just ask [EMAIL PROTECTED] to install them. > Thanks. I just managed to try with the gcc-snapshot currently on voltaire, and the problem persists. I can try with 3.0 if that will help. > > dpkg --fsys-tarfile | tar xf - > > export GCC_EXEC_PREFIX=$HOME/usr/lib/gcc-lib/ > > export LD_LIBRARY_PATH=$HOME/lib:$HOME/usr/lib > > export LIBRARY_PATH=$HOME/lib:$HOME/usr/lib > > export C_INCLUDE_PATH=$HOME/usr/include > > ln -s gcc-??? usr/bin/gcc > > export PATH=$HOME/usr/bin:$PATH > > > > but this isn't working of late anymore, due to > > > > 1) dependencies on latest libc, which in turn depends on latest ld.so, > >which I can't install as a user > > Sure you can, it's just a bit awkward to use. A couple of wrapper > scripts a la > #!/bin/sh > exec $HOME/lib/ld.so --library-path $HOME/lib:$HOME/usr/lib \ > $HOME/usr/bin/gcc $* > Thanks very much for this. Take care, > > 2) oddities with stdlib.h installed with the above procedure. Some > >defines are missing. > > It should work, but you'll have to be more specific about the problems. > > -- > Daniel Jacobowitz > MontaVista Software Debian GNU/Linux Developer > > > -- Camm Maguire[EMAIL PROTECTED] == "The earth is but one country, and mankind its citizens." -- Baha'u'llah
Bug#182795: gcc-3.2: mpqc build fails on MIPS with 'Branch out of range' error
On Fri, Feb 28, 2003 at 12:00:35AM +0100, Michael Banck wrote: > Package: gcc-3.2 > Version: 1:3.2.3-0pre2 > Severity: normal > > Hi, > > compiling mpqc on MIPS results in this error: > > /usr/bin/gcc-3.2 -DHAVE_CONFIG_H -D_REENTRANT -I../../../../../src/lib > -I/build/buildd/mpqc-2.1.3/include -I/build/buildd/mpqc-2.1.3/src/lib -O0 > -Wall -c /build/buildd/mpqc-2.1.3/src/lib/chemistry/qc/dft/lebedev.c > -o lebedev.o > /tmp/ccIsYgSV.s: Assembler messages: > /tmp/ccIsYgSV.s:361: Error: Branch out of range > /tmp/ccIsYgSV.s:366: Error: Branch out of range > [...] > /tmp/ccIsYgSV.s:19541: Error: Branch out of range > /tmp/ccIsYgSV.s:22425: Error: Branch out of range > make[6]: *** [lebedev.o] Error 1 > make[6]: Leaving directory > `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry/qc/dft' > make[5]: *** [default] Error 1 > make[5]: Leaving directory > `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry/qc' > make[4]: *** [default] Error 1 > make[4]: Leaving directory > `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry' > make[3]: *** [default] Error 1 > make[3]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib' > make[2]: *** [default] Error 1 > make[2]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src' > make[1]: *** [default] Error 1 > make[1]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static' > make: *** [build-static-stamp] Error 2 > > see http://buildd.debian.org/fetch.php?&pkg=mpqc&ver=2.1.3-2&arch=mipsel&; \ > stamp=104604&file=log&as=raw for the full buildd log. > > This error also occured on gcc-2.95, I did not file it earlier because I > was hoping that it might be gone in gcc-3.2. The first builds in early > 2002 were done with -O and then with -O0 afterwards. > > You can get the source file at > > http://people.debian.org/~mbanck/lebedev.c FYI, there should be a new binutils which avoids this issue "soon". It's a compiler bug, though - someone should try using gcc-snapshot. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
