gcc-3.0_3.0.4ds3-3_i386.changes ACCEPTED

Accepted: cpp-3.0-doc_3.0.4-3_all.deb to pool/main/g/gcc-3.0/cpp-3.0-doc_3.0.4-3_all.deb cpp-3.0_3.0.4-3_i386.deb to pool/main/g/gcc-3.0/cpp-3.0_3.0.4-3_i386.deb fastjar_3.0.4-3_i386.deb to pool/main/g/gcc-3.0/fastjar_3.0.4-3_i386.deb fixincludes_3.0.4-3_i386.deb to

gcc-2.95_2.95.4.ds9-4_i386.changes ACCEPTED

Accepted: chill-2.95_2.95.4-4_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-4_i386.deb cpp-2.95-doc_2.95.4-4_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-4_all.deb cpp-2.95_2.95.4-4_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-4_i386.deb g++-2.95_2.95.4-4_i386.deb to

Bug#136359: marked as done (g77-2.95: [ALPHA] Please rebuild libg2c.a with -mieee)

Your message dated Sun, 10 Mar 2002 07:02:15 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#136359: fixed in gcc-2.95 2.95.4.ds9-4 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

Bug#136659: unstable+testing: very unstable (SIGSEGV+SIGBUS due to gcc)

Bernd Eckenfels writes: I have the feeling we have a very big GCC Problem in unstable and testing. Some -O2 optimizations of gcc cause SIGBUS on aligned architectures (SPARC), and now even on intel I get regularly SIGSEGVs. I have a few packages which received those reports, and it looks to me