[bts-link] source package gcj-4.2

# # bts-link upstream status pull for source package gcj-4.2 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #437470 # * http://gcc.gnu.org/PR21821 # * remote status changed: (?) -> RESOLVED # * remote resolution cha

[bts-link] source package gcc-4.1

# # bts-link upstream status pull for source package gcc-4.1 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #390693 # * http://gcc.gnu.org/PR27880 # * remote status changed: REOPENED -> NEW usertags 390693 - status-R

[bts-link] source package gcc-3.4

# # bts-link upstream status pull for source package gcc-3.4 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #117765 # * http://gcc.gnu.org/PR179 # * remote status changed: RESOLVED -> REOPENED # * remote resolution

Bug#431984: [hppa] ICE: verify_ssa failed (expected an SSA_NAME object in statement)

* Frank Lichtenheld <[EMAIL PROTECTED]> [2007-07-06 15:41]: > Happened while trying to build a current linux-2.6 from Linus' tree: Can you still reproduce this bug? I cannot with gcc-snapshot 20070720-1 (the latest on hppa). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email

Bug#434852: Simply removed on alpha?

Hello, I read in http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=434852 * Don't build the cacerts file on alpha (closes: #434852). From the build log, I don't see any explanation given (except for the initial failure). Will building return (i.e. is it only a temporary measure)? G

Bug#439836: gdc-4.1: generates invalid assembler code

Package: gdc-4.1 Version: 0.23-4.1.2-15 Severity: normal gdc generates invalid assember code for the following fragment: void foo (int i) { switch (i) { case 1: { static int x = 1; break; } case 2: { static int x = 2; break; } } } ; gdc -c bug.d /tmp/

Processing of gcc-defaults_1.59_i386.changes

gcc-defaults_1.59_i386.changes uploaded successfully to localhost along with the files: gcc-defaults_1.59.dsc gcc-defaults_1.59.tar.gz cpp_4.1.2-9_i386.deb gcc_4.1.2-9_i386.deb gcc-multilib_4.1.2-9_i386.deb gnat_4.1.2-9_i386.deb g++_4.1.2-9_i386.deb g++-multilib_4.1.2-9_i386.deb g

gcc-defaults override disparity

There are disparities between your recently accepted upload and the override file for the following file(s): g++-multilib_4.1.2-9_i386.deb: package says priority is optional, override says standard. gcc-multilib_4.1.2-9_i386.deb: package says priority is optional, override says standard. gfortra

gcc-defaults_1.59_i386.changes ACCEPTED

Accepted: cpp_4.1.2-9_i386.deb to pool/main/g/gcc-defaults/cpp_4.1.2-9_i386.deb g++-multilib_4.1.2-9_i386.deb to pool/main/g/gcc-defaults/g++-multilib_4.1.2-9_i386.deb g++_4.1.2-9_i386.deb to pool/main/g/gcc-defaults/g++_4.1.2-9_i386.deb g77_3.4.6-28_i386.deb to pool/main/g/gcc-defaults/g7