no anonymous cvs access for debian-gcc

2003-05-17 Thread Jack Howarth
Does anyone know if the anonymous cvs access to the different branches of debian-gcc on cvs.debian.org has been disabled on purpose? I am trying to checkout the current gcc-3.3 package with... cvs -z 9 -d :pserver:[EMAIL PROTECTED]:/cvs/debian-gcc login null password cvs -z 9 -d

gcc-defaults_1.6_i386.changes ACCEPTED

2003-05-17 Thread Debian Installer
Accepted: chill_2.95.4-21_i386.deb to pool/main/g/gcc-defaults/chill_2.95.4-21_i386.deb cpp_3.3-1_i386.deb to pool/main/g/gcc-defaults/cpp_3.3-1_i386.deb g++_3.3-1_i386.deb to pool/main/g/gcc-defaults/g++_3.3-1_i386.deb g77_3.3-1_i386.deb to pool/main/g/gcc-defaults/g77_3.3-1_i386.deb

Bug#190823: marked as done (gcc-defaults should provide c99 utility)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 04:32:08 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#190823: fixed in gcc-defaults 1.6 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

Bug#188513: #188513: gcc generates invalid assembler on arm

2003-05-17 Thread Philip Blundell
This looks rather similar to #192634, though the bit about source register same as write-back base is slightly worrying. A patch for that bug is in debian-gcc cvs for both 3.2 and 3.3 now, so it might be worth making new packages for testing. p.

Bug#188513: #188513: gcc generates invalid assembler on arm

2003-05-17 Thread Matthias Klose
Philip Blundell writes: This looks rather similar to #192634, though the bit about source register same as write-back base is slightly worrying. A patch for that bug is in debian-gcc cvs for both 3.2 and 3.3 now, so it might be worth making new packages for testing. thanks. making the 3.3

Processed: Re: Bug#193333: apt-get no longer runs on 386 CPUs (Illegal instruction)

2003-05-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 19 libstdc++5 Bug#19: apt-get no longer runs on 386 CPUs (Illegal instruction) Bug reassigned from package `apt' to `libstdc++5'. merge 19 185662 Bug#185662: libstdc++5: Illegal instruction on 386 CPUs Bug#19: apt-get no

Processed: Re: Processed: Re: Bug#193333: apt-get no longer runs on 386 CPUs (Illegal instruction)

2003-05-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 19 important Bug#19: apt-get no longer runs on 386 CPUs (Illegal instruction) Severity set to `important'. merge 19 185662 Bug#185662: libstdc++5: Illegal instruction on 386 CPUs Bug#19: apt-get no longer runs on 386 CPUs

Results for 3.3 (Debian) testsuite on hppa-unknown-linux-gnu

2003-05-17 Thread Matthias Klose
LAST_UPDATED: Native configuration is hppa-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/compat/break/bitfield7 x_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

Results for 3.3 (Debian) testsuite on i386-pc-linux-gnu

2003-05-17 Thread Matthias Klose
LAST_UPDATED: Native configuration is i386-pc-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/tls/init-2.C (test for excess errors) XPASS: g++.other/init5.C Execution test === g++ Summary === # of expected passes7997 # of unexpected

gcc-3.3_3.3ds9-1_i386.changes ACCEPTED

2003-05-17 Thread Debian Installer
Accepted: cpp-3.3-doc_3.3-1_all.deb to pool/main/g/gcc-3.3/cpp-3.3-doc_3.3-1_all.deb cpp-3.3_3.3-1_i386.deb to pool/main/g/gcc-3.3/cpp-3.3_3.3-1_i386.deb fastjar_3.3-1_i386.deb to pool/main/g/gcc-3.3/fastjar_3.3-1_i386.deb fixincludes_3.3-1_i386.deb to

gcc-3.3 override disparity

2003-05-17 Thread Debian Installer
There are disparities between your recently accepted upload and the override file for the following file(s): gcc-3.3_3.3-1_i386.deb: package says priority is standard, override says optional. g++-3.3_3.3-1_i386.deb: package says priority is standard, override says optional.

gcc-3.3_3.3ds9-1_hppa.changes ACCEPTED

2003-05-17 Thread Debian Installer
Accepted: cpp-3.3_3.3-1_hppa.deb to pool/main/g/gcc-3.3/cpp-3.3_3.3-1_hppa.deb fastjar_3.3-1_hppa.deb to pool/main/g/gcc-3.3/fastjar_3.3-1_hppa.deb fixincludes_3.3-1_hppa.deb to pool/main/g/gcc-3.3/fixincludes_3.3-1_hppa.deb g++-3.3_3.3-1_hppa.deb to

Bug#95318: marked as done ([fixed on 3.3/HEAD: PR optimization/2962] unnecessary cwtl)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:57 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#95318: fixed in gcc-3.3 1:3.3ds9-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

Bug#88694: marked as done ([fixed] [PR c++/3936] flightgear: build failure on sparc)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#88694: fixed in gcc-3.3 1:3.3ds9-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

Bug#93708: marked as done ([fixed in gcc-3.0] man versus info inconsistency (-W and -Wall))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:57 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#93708: fixed in gcc-3.3 1:3.3ds9-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

Bug#94891: marked as done ([fixed in 3.0] %zd printf spec generates warning, even in c9x mode)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:57 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#94891: fixed in gcc-3.3 1:3.3ds9-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

Bug#87540: marked as done ([fixed in 3.0] ICE when using -mno-ieee-fp and -march=i686)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#87540: fixed in gcc-3.3 1:3.3ds9-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

Bug#65686: marked as done ([fixed in gcc-3.1] Internal compiler error (signal 11))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#65686: fixed in gcc-3.3 1:3.3ds9-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

Bug#81122: marked as done ([fix 3.1: PR c++/3494] Internal compiler error (with wrong code, though))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:55 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#81122: fixed in gcc-3.3 1:3.3ds9-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

Bug#90666: marked as done ([fixed in gcc-3.0] reproducible internal compiler error)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:57 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#90666: fixed in gcc-3.3 1:3.3ds9-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

Bug#85934: marked as done ([fixed in g++-3.0] ICE on template class)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#85934: fixed in gcc-3.3 1:3.3ds9-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

Bug#65406: marked as done ([fixed in gcc-3.0] gcc -dumpspecs undocumented)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#65406: fixed in gcc-3.3 1:3.3ds9-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

Bug#83550: marked as done ([PR target/491] can't compile php4 on arm)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#83550: fixed in gcc-3.3 1:3.3ds9-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

Bug#68987: marked as done ([fixed in gobjc-2.97] Interface to garbage collector is undocumented.)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:55 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#68987: fixed in gcc-3.3 1:3.3ds9-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

Bug#59232: marked as done ([fixed upstream 20010109] gcc -c -MD x/y.c -o x/y.o leaves y.d in the current directory)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#59232: fixed in gcc-3.3 1:3.3ds9-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

Bug#64832: marked as done ([fixed in gcc-3.1] gcc optimizer bug on m68k)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#64832: fixed in gcc-3.3 1:3.3ds9-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

Bug#83363: marked as done ([fixed in g++-3.0] g++ breaks a simple sort program when compiling at -O2)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#83363: fixed in gcc-3.3 1:3.3ds9-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

Bug#56867: marked as done ([fix with libstdc++-v3 20000720] program compiled -O3 -malign-double segfaults in ofstream::~ofstream)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:53 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#56867: fixed in gcc-3.3 1:3.3ds9-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

Bug#64628: marked as done ([fixed in 2.96 CVS 20000720] gcc -fpack-struct)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#64628: fixed in gcc-3.3 1:3.3ds9-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

Bug#61806: marked as done ([fixed in g++-3.0] [PR114] __attribute__ ((constructor)) doesn't work with C++)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#61806: fixed in gcc-3.3 1:3.3ds9-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

Bug#70743: marked as done ([fixed in gcc-3.0 and gcc-3.1] [alpha] g++ -O2 optimization error)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:55 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#70743: fixed in gcc-3.3 1:3.3ds9-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

Bug#67631: marked as done ([fixed in upstream CVS 20000720] Compiler error with -O2)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#67631: fixed in gcc-3.3 1:3.3ds9-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

Bug#46181: marked as done ([fixed in 2.96] c++ error message improvement suggestion)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:51 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#46181: fixed in gcc-3.3 1:3.3ds9-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

Bug#51456: marked as done ([fixed in upstream gcc-20000114] another gcc optimization error)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:52 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#51456: fixed in gcc-3.3 1:3.3ds9-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

Bug#43001: marked as done ([fixed in 3.0] [alpha] gcc 2.95.2 19990906 Internal compiler error in `fixup_var_refs_1')

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:51 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#43001: fixed in gcc-3.3 1:3.3ds9-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

Bug#45440: marked as done ([fixed in g++-3.1] __attribute__((unused)) is ignored in C++)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:51 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#45440: fixed in gcc-3.3 1:3.3ds9-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

Bug#43170: marked as done ([PR 40: deprecated in 3.0] Result naming doesn't work for functions defined in a class)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:51 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#43170: fixed in gcc-3.3 1:3.3ds9-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

Bug#33786: marked as done ([fixed upstream 001117] uncaught floating point exception causes gcc internal compiler error)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:50 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#33786: fixed in gcc-3.3 1:3.3ds9-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

Bug#94701: marked as done ([PR optimization/2960] Duplicate loop conditions even with -Os)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:57 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#94701: fixed in gcc-3.3 1:3.3ds9-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

Bug#83221: marked as done ([fixed in 3.0] g++ dies with internal error)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:55 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#83221: fixed in gcc-3.3 1:3.3ds9-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

Bug#62309: marked as done ([fixed in 3.0] Internal compiler error: program cc1obj got fatal signal 11)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#62309: fixed in gcc-3.3 1:3.3ds9-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

Bug#34876: marked as done ([fixed upstream 001117] vtable thunks implementation is broken)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:50 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#34876: fixed in gcc-3.3 1:3.3ds9-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

Bug#189702: marked as done ([PR 10580] [fixed in 3.3] [powerpc] ICE with -O -Wunreachable-code)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:49 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#189702: fixed in gcc-3.3 1:3.3ds9-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

Bug#84969: marked as done ([PR target/491] can't compile php4 on arm)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#83550: fixed in gcc-3.3 1:3.3ds9-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

Bug#187910: marked as done ([fixed in 3.3] ICE while compiling mozilla with -march=pentium4)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:49 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#187910: fixed in gcc-3.3 1:3.3ds9-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

Bug#184800: marked as done ([fixed in 3.3] ICE while building mplayer)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:48 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#184800: fixed in gcc-3.3 1:3.3ds9-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

Bug#181679: marked as done ([fixed in gcc-3.3] Preelaborate, exceptions, and -gnatN)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:48 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#181679: fixed in gcc-3.3 1:3.3ds9-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

Bug#51651: marked as done ([done with gcc-2.96] please use --enable-nls --enable-c-mbchar)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:52 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#51651: fixed in gcc-3.3 1:3.3ds9-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

Bug#59005: marked as done ([fix with libstdc++-v3] compilation error in stl_alloc.h with -fhonor-std)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:53 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#59005: fixed in gcc-3.3 1:3.3ds9-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

Bug#58219: marked as done ([fixed in upstream gcc-20000116] Compiler barfs with -O on specific file)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:53 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#58219: fixed in gcc-3.3 1:3.3ds9-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

Bug#180750: marked as done ([PR target/9790] [3.2 regression on arm, fixed in 3.3] ICE with -O2 (change_address_1, at emit-rtl.c:1945))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:48 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#180750: fixed in gcc-3.3 1:3.3ds9-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

Bug#55291: marked as done ([alpha; fixed in upstream CVS] internal compiler compiling hatman)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:52 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#55291: fixed in gcc-3.3 1:3.3ds9-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

Bug#179597: marked as done ([Fixed with 3.3 20030129 (prerelease)] Internal compiler error: Error reporting routines re-entered.)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:47 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#179597: fixed in gcc-3.3 1:3.3ds9-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

Bug#180493: marked as done ([fixed in 3.3] m68k - ICE in instantiate_virtual_regs_1, at function.c:3980)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:48 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#180493: fixed in gcc-3.3 1:3.3ds9-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

Bug#48530: marked as done (g++ [fixed in 2.96 CVS Feb 2000] [alpha]: internal compiler error building open-amulet)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:52 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#48530: fixed in gcc-3.3 1:3.3ds9-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

Bug#50529: marked as done ([fixed in g++-3.0] volatile undefined...)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:52 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#50529: fixed in gcc-3.3 1:3.3ds9-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

Bug#178965: marked as done ([PR 10113, 3.2/3.3/3.4 sparc regression] ICE when optimizing (gen_reg_rtx, at emit-rtl.c:662))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:47 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#178965: fixed in gcc-3.3 1:3.3ds9-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

Bug#2910: marked as done ([fixed in gcc-3.1] GCC accepts multi-line strings without \ or c)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:50 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#2910: fixed in gcc-3.3 1:3.3ds9-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

Bug#185903: marked as done ([PR 10194] [3.2 regression, fixed in 3.3] [arm] gcc optimization error with -O2, affecting bison)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:49 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#185903: fixed in gcc-3.3 1:3.3ds9-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

Bug#178596: marked as done ([fixed in 3.3] {s390} operand out of range at assembly time when using -O2)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:47 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#178596: fixed in gcc-3.3 1:3.3ds9-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

Bug#178830: marked as done ([fixed in 3.3] {ia64} gcc-3.2 fails w/ optimization)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:47 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#178830: fixed in gcc-3.3 1:3.3ds9-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

Bug#176387: marked as done ([PR optimization/9279, fixed in 3.3] {sparc} gcc-3.2 regression (wrong code))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:47 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#176387: fixed in gcc-3.3 1:3.3ds9-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

Bug#180567: marked as done ([fixed in 3.3] Broken zip file handling)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:48 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#180567: fixed in gcc-3.3 1:3.3ds9-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

Bug#170994: marked as done ([fixed in 3.x] ICE on __builtin_memset(s, 0, -1) (2.95 only))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:46 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#170994: fixed in gcc-3.3 1:3.3ds9-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

Bug#168346: marked as done ([fixed in 3.x] C99 symbols in limits.h not defined)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:46 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#168346: fixed in gcc-3.3 1:3.3ds9-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

Bug#168310: marked as done ([fixed in 3.3] [PR c++/8598] xmmintrin.h broken for c++)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:46 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#168310: fixed in gcc-3.3 1:3.3ds9-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

Bug#35477: marked as done ([fixed upstream 001117] C++ class mishandling)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:50 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#34876: fixed in gcc-3.3 1:3.3ds9-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

Bug#184862: marked as done ([fixed in 3.3] static fpos_t gives internal compiler error)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:49 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#184862: fixed in gcc-3.3 1:3.3ds9-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

Bug#184753: marked as done ([PR 10084] [3.2/3.3 regression]: alpha ICE while building ddd/kseg)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:48 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#184753: fixed in gcc-3.3 1:3.3ds9-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

Bug#186299: marked as done ([fixed in 3.3] [PR 10315] [powerpc] ICE: in extract_insn, at recog.c:2175 building php3)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:49 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#186299: fixed in gcc-3.3 1:3.3ds9-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

Bug#42662: marked as done ([fixed in 2.96 CVS 20000720] templated friend)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:51 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#42662: fixed in gcc-3.3 1:3.3ds9-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

Bug#165992: marked as done ([docs fixed in 3.2] __builtin_return_address doesn't work properly)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:46 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#165992: fixed in gcc-3.3 1:3.3ds9-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

Bug#148603: marked as done ([fixed in g++-3.1] crash when template declared after use)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#148603: fixed in gcc-3.3 1:3.3ds9-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

Bug#137382: marked as done ([fixed in gcc-3.0/3.1] -Q option to gcc appears twice in the documentation)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:43 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#137382: fixed in gcc-3.3 1:3.3ds9-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

Bug#105309: marked as done ([fixed in 3.3/HEAD: PR optimization/3995] i386 optimisation: joining tests)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:41 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#105309: fixed in gcc-3.3 1:3.3ds9-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

Bug#136630: marked as done ([fixed in gcc-3.0/3.1] gcc chokes (internal error) on invalid extended asm)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:43 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#136630: fixed in gcc-3.3 1:3.3ds9-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

Bug#105569: marked as done ([fixed in g++-3.0] [mips] g++ exception catching does not work...)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:42 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#105569: fixed in gcc-3.3 1:3.3ds9-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

Bug#118670: marked as done ([not a bug/fixed in libgcc1] libgcc.a symbols end up exported by shared libraries)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:42 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#118670: fixed in gcc-3.3 1:3.3ds9-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

Bug#167439: marked as done ([fixed in gcc-3.x] stdbool.h broken)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:46 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#167439: fixed in gcc-3.3 1:3.3ds9-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

Bug#151196: marked as done ([fixed in gcc-3.x] gcc-2.95.4-9 ICE in kernel (matroxfb) code)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:44 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#151196: fixed in gcc-3.3 1:3.3ds9-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

Bug#178909: marked as done ([PR 10114, 3.2/3.3/3.4 sparc regression] ICE when optimizing (mem_loc_descriptor, at dwarf2out.c:7903))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:47 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#178909: fixed in gcc-3.3 1:3.3ds9-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

Bug#152315: marked as done ([fixed in g++-3.x] g++-2.95-3/4 template and virtual inheritance bug)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:45 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#152315: fixed in gcc-3.3 1:3.3ds9-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

Bug#188527: marked as done ([fixed in 3.3] [PR 10427] [3.2/3.3/3.4 regression] Stack corruption with variable-length automatic arrays and virtual destructors)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:49 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#188527: fixed in gcc-3.3 1:3.3ds9-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

Bug#161615: marked as done ([fixed in 3.3] -print-file-name sometimes fails)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:45 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#161615: fixed in gcc-3.3 1:3.3ds9-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

Bug#27878: marked as done ([new options in 20000109] automatic dependency dehairification request)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:50 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#27878: fixed in gcc-3.3 1:3.3ds9-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

Bug#65687: marked as done ([fixed upstream 001117] Internal compiler error)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:54 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#65687: fixed in gcc-3.3 1:3.3ds9-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

Bug#55967: marked as done ([fixed in 2.96 CVS 20000720] internal compiler error (testcase attached))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:53 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#55967: fixed in gcc-3.3 1:3.3ds9-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

Bug#20695: marked as done (regparm/profiling breakage (fixed with gcc-3.0))

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:50 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#20695: fixed in gcc-3.3 1:3.3ds9-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

Bug#193689: gcc-3.3: GCC 3.3 uninstallable on i386

2003-05-17 Thread Javier
Package: gcc-3.3 Version: 1:3.3-1 Severity: normal The package libgcc1 depends of nonexistent lib64gcc1, so it is not installable. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux drizzt 2.4.20-ck4 #1 sáb mar 22 17:17:18 CET 2003 i686 Locale: [EMAIL

Bug#80468: marked as done ([fixed in gobjc-3.1] @protocol forward definitions do not work)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:55 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#80468: fixed in gcc-3.3 1:3.3ds9-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

Bug#88260: marked as done ([fixed in g++-3.0] No warning for missing return in non-void member func)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#88260: fixed in gcc-3.3 1:3.3ds9-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

Bug#47981: marked as done ([fixed in upstream 20000518] [alpha] Mutt segv on viewing list of attachments)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:52 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#47981: fixed in gcc-3.3 1:3.3ds9-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

Bug#172956: marked as done ([fixed in gcc-3.x] Sparc GCC issue with -mcpu=ultrasparc)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:47 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#172956: fixed in gcc-3.3 1:3.3ds9-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

Bug#162074: marked as done ([fix in 3.2] Warning when including stl.h)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:46 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#162074: fixed in gcc-3.3 1:3.3ds9-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

Bug#158704: marked as done ([fix in 3.2] gcc doesn't warn about unreachable code)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:45 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#158704: fixed in gcc-3.3 1:3.3ds9-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

Bug#85535: marked as done ([fixed in gcc-3.1, PR optimization/3508]: builtin memcmp() could be optimised)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#85535: fixed in gcc-3.3 1:3.3ds9-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

Bug#53698: marked as done ([fixed upstream 001117] internal compiler error with templates)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:52 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#53698: fixed in gcc-3.3 1:3.3ds9-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

Bug#165110: marked as done ([fixed in gcc-3.x] undocumented option -pthread)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:46 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#165110: fixed in gcc-3.3 1:3.3ds9-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

Bug#156450: marked as done ([fixed in 3.x] doesn't handle empty args in macro function if there is only one arg)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:45 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#156450: fixed in gcc-3.3 1:3.3ds9-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

Bug#90363: marked as done ([fixed in g77-3.0] f77 miscompiles PIC on arm)

2003-05-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 May 2003 17:32:56 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#90363: fixed in gcc-3.3 1:3.3ds9-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

  1   2   >