Processed: tagging 487115

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.30 > tags 487115 + fixed-upstream Bug#487115: gcc-4.3: gcc 4.3.1 cannot be used to compile the Linux kernel (bad code generation) Tags were: upstream Tags added: fixed-upstream > End of

Bug#479115: marked as done (libffi4 has broken dependencies)

Your message dated Mon, 23 Jun 2008 22:42:38 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: libffi4 has broken dependencies has caused the Debian Bug report #479115, regarding libffi4 has broken dependencies to be marked as done. This means that you claim that the problem has bee

Bug#487075: marked as done (warning: will never be executed)

Your message dated Tue, 24 Jun 2008 00:18:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: warning: will never be executed has caused the Debian Bug report #487075, regarding warning: will never be executed to be marked as done. This means that you claim that the problem has been

Processed: Re: warning: will never be executed

Processing commands for [EMAIL PROTECTED]: > tag 487075 + wontfix Bug#487075: warning: will never be executed There were no tags set. Tags added: wontfix > tag 487075 + fixed-upstream Bug#487075: warning: will never be executed Tags were: wontfix Tags added: fixed-upstream > thanks Stopping proc

Processed: pending gcc bugs

Processing commands for [EMAIL PROTECTED]: > tag 483609 + pending Bug#483609: gcc-4.1: on hurd-i386 -fstack-protector tries to link with libssp_nonshared Tags were: patch Tags added: pending > tag 483612 + pending Bug#483612: gcc-4.2: on hurd-i386 -fstack-protector tries to link with libssp_non

Bug#487406: Code not compiled properly on ARM

is this arm only, or armel as well? Matthias Enrico Zini writes: > Package: g++-4.3 > Version: 4.3.1-2 > Severity: normal > > Hello, > > the attached code seems to be the minimal test case to reproduce the > current build failure of libept on ARM. > > Normally, that code should not do anythi

Processed: remove security tag for gcc bug report

Processing commands for [EMAIL PROTECTED]: > tag 482698 - security Bug#482698: CVE-2008-1685: removes possible protection mechanism against overflows Tags were: security Tags removed: security > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking syst

Bug#487396: Missing link error on ARM

Is this arm only, or armel as well? Matthias Enrico Zini writes: > Package: g++-4.3 > Version: 4.3.1-2 > Severity: normal > > Hello, > > while trying to investigate why libept does not build on ARM, I came up > with the attached source code. On any system, it gives a link time > error while

Bug#369064: Patch already in deb but deactivated

Goswin von Brederlow writes: > Hi, > > I believe the gcc source already has a patch for multiarch include and library > directories but they are deactiveated in rules.defs. > > Can you comment on the functionality of them? no, this one is obsolete. removed in svn. Matthias -- To UNSUBSCRI

Bug#487776: g++-4.3: g++ segfault when compiling with -ftree-parallelize-loops=2

Package: g++-4.3 Version: 4.3.1-2 Severity: normal When compiling a pretty large file (8,000+ lines) with -ftree-parallelize-loops=2, g++ segfaults, and leaves around a ~260MB corefile. I couldn't figure out how to get symbols for the backtrace, but looking at the addresses themselves, it seemed l

Bug#484784: marked as done (gcc-4.3: -O2 -O3 - wrong arguments are passing to inlined body of function)

Your message dated Tue, 24 Jun 2008 08:16:33 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#484784: gcc-4.3: -O2 -O3 - wrong arguments are passing to inlined body of function has caused the Debian Bug report #484784, regarding gcc-4.3: -O2 -O3 - wrong arguments are passing to