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 message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 479115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479115 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libffi4 Version: 4.3.0-3 Running Debian Sid with 2.6.25 kernel. /lib/libc.so.6 --> libc-2.7.so Ran apt-get update followed by apt-get install libffi4 and i get the following: The following packages have unmet dependencies: libffi4: Depends: gcc-4.3-base ( = 4.3.0-3) but 4.3.0-4 is to be installed E: Broken packages Thanks --- End Message --- --- Begin Message --- libffi4-dev/libffi4 is not part of testing/unstable anymore. --- End Message ---
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 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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
487075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487075
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libstdc++6-4.1-dev in etch of architecture i386
When compiling programs which use
"/usr/include/c++/4.1.2/bits/streambuf_iterator.h" with gcc, and including the
flag "-Wunreachable-code", the compiler informs me that the header file
contains unreachable code. Now I know this is not an "error", but maybe one
could optimize the code found in the header based on the compilers suggestions.
I am using:
Linux 2.6.18-6-686 i686 GNU/Linux (Debian Etch)
Sample code (taken from
"http://www2.roguewave.com/support/docs/leif/sourcepro/html/stdlibref/istreambuf-iterator.html";):
//
// istreambuf_iterator.cpp
//
#include// for cout, endl
#include // for ofstream, istreambuf_iterator
#include // for tmpnam () and remove ()
int main ( )
{
// create a temporary filename
const char *fname = tmpnam (0);
if (!fname)
return 1;
// open the file is_iter.out for reading and writing
std::ofstream out (fname, std::ios::out | std::ios::in |
std::ios::trunc);
// output the example sentence into the file
out << "Ceci est un simple exemple pour démontrer le\n"
"fonctionnement de istreambuf_iterator.";
// seek to the beginning of the file
out.seekp (0);
// construct an istreambuf_iterator pointing to
// the ofstream object underlying streambuffer
std::istreambuf_iterator >
iter (out.rdbuf ());
// construct an end of stream iterator
const std::istreambuf_iterator > end;
std::cout << std::endl;
// output the content of the file
while (!iter.equal (end)) {
// use both operator++ and operator*
std::cout << *iter++;
}
std::cout << std::endl;
// remove temporary file
remove (fname);
return 0;
}
Sample compiling run:
g++ -Wunreachable-code -o prog main.cpp
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/fstream: In
constructor ‘std::basic_ofstream<_CharT, _Traits>::basic_ofstream(const
char*, std::_Ios_Openmode) [with _CharT = char, _Traits =
std::char_traits]’:
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/fstream:573:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/fstream:573:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/fstream:573:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/fstream:573:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/fstream:575:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/fstream:576:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/bits/basic_ios.h:
In constructor ‘std::basic_ios<_CharT, _Traits>::basic_ios() [with
_CharT = char, _Traits = std::char_traits]’:
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/bits/basic_ios.h:447:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/ostream: In
constructor ‘std::basic_ostream<_CharT, _Traits>::basic_ostream() [with
_CharT = char, _Traits = std::char_traits]’:
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/ostream:341:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/ostream:341:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/ostream:341:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/ostream:341:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/ostream:341:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/ostream: In
destructor ‘std::basic_ostream<_CharT, _Traits>::~basic_ostream() [with
_CharT = char, _Traits = std::char_traits]’:
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/ostream:113:
warning: will never be executed
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4
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 processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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_nonshared Tags were: patch Tags added: pending > tag 483613 + pending Bug#483613: gcc-4.3: on hurd-i386 -fstack-protector tries to link with libssp_nonshared Tags were: patch Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 anything, but on ARM, it segfaults. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 building it. On ARM, only when invoking g++, only with > -fPIC, it links fine, then running the program segfaults. > > To reproduce, install g++ 4.3 on ARM, then run: > > g++-4.3 -fPIC -o main1 main1.cpp > > We have been working on minimising this test code since a whole day, and > we did not manage to make it smaller than this. Fiddling with this code > further (like removing a template parameter, or removing the std > namespace) makes the linker error properly appear. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 like the stack was corrupted, and had been overwritten with a bunch of ints (during some parts of the backtrace, places, the frame addresses were increasing monotonically at 4-byte increments, which seems odd for actual function calls). testcase is at http://web.mit.edu/~xsdg/www/g++_segfault_testcase.tar.bz2 Also, there was a secondary part of this behavior that I was not able to reproduce. When I removed the dependency flags (-M*), the segfault went away and remained gone when I re-added them (without removing -ftree-parallelize-loops at all). At that point, I had to `make clean` and then remake for the segfault to recur. As mentioned, though, I have had trouble reproducing this part of the behavior. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25.7 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages g++-4.3 depends on: ii gcc-4.3 4.3.1-2The GNU C compiler ii gcc-4.3-base 4.3.1-2The GNU Compiler Collection (base ii libc6 2.7-12 GNU C Library: Shared libraries ii libgmp3c2 2:4.2.2+dfsg-3 Multiprecision arithmetic library ii libmpfr1ldbl 2.3.1.dfsg.1-2 multiple precision floating-point ii libstdc++6-4.3-dev4.3.1-2The GNU Standard C++ Library v3 (d Other possibly-relevant testcase compilation dependencies: $dpkg -l *gtk* *atk* *cairo* *pango* *glib* *freetype* *libpng* *pixman* \ > | grep '^ii' | cut -c1-60 | grep ' lib' ii libatk1.0-0 1.22.0-1 ii libatk1.0-dev1.22.0-1 ii libavahi-glib-dev0.6.22-3 ii libavahi-glib1 0.6.22-3 ii libcairo21.6.4-6 ii libcairo2-dev1.6.4-6 ii libcairomm-1.0-1 1.6.0-1 ii libdbus-glib-1-2 0.76-1 ii libdbus-glib-1-dev 0.76-1 ii libfreetype6 2.3.6-1 ii libfreetype6-dev 2.3.6-1 ii libglib2.0-0 2.17.0-1 ii libglib2.0-dev 2.17.0-1 ii libglib2.0-doc 2.16.3-2 ii libglibmm-2.4-1c2a 2.16.1-1 ii libgtk2.0-0 2.12.10-2 ii libgtk2.0-common 2.12.9-3 ii libgtk2.0-dev2.12.10-2 ii libgtkhtml2-02.11.1-2 ii libgtkhtml2-dev 2.11.1-2 ii libgtkimageview-dev 1.6.1-2 ii libgtkimageview0 1.6.1-2 ii libgtkmm-2.4-1c2a1:2.12.7-1 ii libgtksourceview-common 1.8.5-1 ii libgtksourceview1.0-01.8.5-1 ii libgtksourceview2.0-02.2.1-1 ii libgtksourceview2.0-common 2.2.1-1 ii libgtkspell0 2.0.10-4 ii libpango1.0-01.20.3-1 ii libpango1.0-common 1.20.3-1 ii libpango1.0-dev 1.20.3-1 ii libpixman-1-00.10.0-2 ii libpixman-1-dev 0.10.0-2 ii libpng12-0 1.2.27-1 ii libpng12-dev 1.2.27-1 ii libpoppler-glib-dev 0.6.4-1 ii libpoppler-glib2 0.6.4-1 ii libpoppler-glib3 0.8.2-2 ii libwxgtk2.6-02.6.3.2.2-2 g++-4.3 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 inlined body of
function
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
484784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484784
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Subject: gcc-4.3: -O2 -O3 - wrong arguments are passing to inlined body of
function
Package: gcc-4.3
Version: 4.3.0-5
Severity: important
Consider this simple program:
---bug.c---
#define N 100
char array[N];
void inline_asm(int iters) {
__asm__ volatile (
#ifdef PRESERVE_ALL_REGS
"pushal \n"
#endif
" xorl %%ebx, %%ebx \n"
"0: \n"
" movzbl (%%eax), %%edx \n"
" addl %%edx, %%ebx \n"
" incl %%eax \n"
" decl %%ecx \n"
" jnz 0b \n"
#ifdef PRESERVE_ALL_REGS
"popal \n"
#endif
: /* no output */
: "a" (array),
"c" (iters)
: "ebx", "edx"
);
}
int main() {
int n = 100;
while (n--)
inline_asm(N);
}
---eof---
Function inline_asm just add all values from array; all modified/input
registers are listed in __asm__ statement.
When program is compiled without any optimization flag, it works ok.
However if compiled with -O3 or -O3 --- segfaults. I quickly analyzed
assembly output, and it is clear, that gcc fully inlined procedure,
however in a while loop only address is restored (%eax), but inner loop
counter (%ecx) isn't. Thus in a second iteration %ecx has value 0, and
loop would execute 0x times, but segfault appear faster.
When sample program is compiled with -O3 -DPRESERVE_ALL_REGS all is
ok, because pair pushal/popal saves and restores all registers.
---bug.s---
main:
# .. snip ...
movl$array, %esi
pushl %ebx
pushl %ecx
movl$100, %ecx <-- ERROR: ecx is loaded only once
.p2align 4,,7
.p2align 3
#while
.L4:
movl%esi, %eax <-- OK: eax is reloaded in every while-iteration
#APP
# 6 "bug.c" 1
xorl %ebx, %ebx
0:
movzbl (%eax), %edx
addl %edx, %ebx
incl %eax
decl %ecx
jnz 0b
# 0 "" 2
#NO_APP
addl$1, %edi
cmpl$100, %edi
jne .L4
#endwhile
# ... snip ...
---cut---
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash
Versions of packages gcc-4.3 depends on:
ii binutils2.18.1~cvs20080103-6 The GNU assembler, linker and bina
ii cpp-4.3 4.3.0-5 The GNU C preprocessor
ii gcc-4.3-base4.3.0-5 The GNU Compiler Collection (base
ii libc6 2.7-12 GNU C Library: Shared libraries
ii libgcc1 1:4.3.0-5GCC support library
ii libgomp14.3.0-5 GCC OpenMP (GOMP) support library
Versions of packages gcc-4.3 recommends:
ii libc6-dev 2.7-12 GNU C Library: Development Librari
--- End Message ---
--- Begin Message ---
On Sat, Jun 07, 2008 at 10:16:36AM +0200, Bastian Blank wrote:
> No bug. You cheated so the compiler is free to do whatever it wants.
Closing.
Bastian
--
Killing is stupid; useless!
-- McCoy, "A Private Little War", stardate 4211.8
--- End Message ---
