Bug#517653: gcc-4.3: warning: comparison with string literal results in unspecified behavior when comparing two different literals

2012-05-05 Thread Kalle Olavi Niemitalo
package gcc-4.3 found 517653 gcc-4.4/4.4.7-1 found 517653 gcc-4.6/4.6.3-1 found 517653 gcc-4.7/4.7.0-3 quit Kalle Olavi Niemitalo k...@iki.fi writes: Compiling this with gcc-4.3 -Wall -c int main (void) { return hello == there; } results in a warning: hoh.c: In function ‘main

Bug#634200: gcc -Wall -Werror -lncurses fails to link wide-character ncursesw functions.

2011-07-18 Thread Kalle Olavi Niemitalo
Ray Dillinger b...@sonic.net writes: display.c starts with the lines: #define _X_OPEN_SOURCE_EXTENDED There is an extra underscore after the X. Correcting that fixes the implicit-declaration error for me. Also, for consistency with other uses of this macro, it would be best to define it

Bug#517653: gcc-4.3: warning: comparison with string literal results in unspecified behavior when comparing two different literals

2009-03-01 Thread Kalle Olavi Niemitalo
Package: gcc-4.3 Version: 4.3.1-4 Severity: minor Compiling this with gcc-4.3 -Wall -c int main (void) { return hello == there; } results in a warning: hoh.c: In function ‘main’: hoh.c:4: warning: comparison with string literal results in unspecified behavior The warning claims the

Bug#517653: gcc-4.3: warning: comparison with string literal results in unspecified behavior when comparing two different literals

2009-03-01 Thread Kalle Olavi Niemitalo
Bastian Blank wa...@debian.org writes: §6.4.5 6) say: | It is unspecified whether these arrays are distinct provided their | elements have the appropriate values. If the arrays resulting from hello and there were not distinct from each other, then their elements would not have the appropriate

Bug#517653: gcc-4.3: warning: comparison with string literal results in unspecified behavior when comparing two different literals

2009-03-01 Thread Kalle Olavi Niemitalo
Falk Hueffner f...@debian.org writes: I can't imagine any sensible code whatsoever that triggers this warning but does not have logical errors. Can you show how it is used? Here are all the source lines from net-snmp 5.2.3-7etch4 that trigger this warning. snmplib/data_list.c:108

autoconf version conflict building gcc-3.3

2005-04-12 Thread Kalle Olavi Niemitalo
I am having trouble building gcc-3.3 1:3.3.5-12 on i386. I first get several FATAL ERRORs: DEB_VERSION='1:3.3.5-12'; export DEB_VERSION; \ debian/patches/autoreconf.dpatch -patch -d /var/tmp/kalle/debian/gcc-3.3-3.3.5/src patching file libtool.m4 FATAL ERROR: Autoconf version 2.50 or higher is

Bug#208981: gcc-3.3: typeof(nonconst+const) is const

2003-09-06 Thread Kalle Olavi Niemitalo
Package: gcc-3.3 Version: 1:3.3.2-0pre1 Severity: minor Try compiling the following function with gcc-3.3 -c const.c. GCC gives assignment of read-only variable warnings on the indicated lines. This shows that __typeof__ treats the corresponding arguments as const. void fn(void) { int n;

Bug#186139: gcc-3.2: [alpha] va_start is off by one

2003-04-13 Thread Kalle Olavi Niemitalo
I tested newer versions of gcc-3.2 and gcc-snapshot. gcc-2.95 2.95.4-17 buggy, won't be fixed gcc-3.0 3.0.4-7 buggy, removed from unstable gcc-3.2 3.2.3-0pre8 buggy gcc-3.3 3.3-0pre2 fixed gcc-snapshot 20030410-1 fixed, unlike 20030314-1

Bug#186139: gcc-3.2: [alpha] va_start is off by one

2003-03-30 Thread Kalle Olavi Niemitalo
Kalle Olavi Niemitalo [EMAIL PROTECTED] writes: No, all these versions have the same bug: gcc-2.95 2.95.4-17 gcc-3.0 3.0.4-7 gcc-3.2 3.2.3-0pre6 gcc-snapshot 20030314-1 However, gcc-3.3 3.3-0pre2 works correctly, and a control-center compiled with it does not suffer from Bug

Bug#186139: gcc-3.2: [alpha] va_start is off by one

2003-03-25 Thread Kalle Olavi Niemitalo
Matthias Klose [EMAIL PROTECTED] writes: - does the code example work with gcc-snapshot? - does the code example work with 2.95 (or 3.0.4)? No, all these versions have the same bug: gcc-2.95 2.95.4-17 gcc-3.0 3.0.4-7 gcc-3.2 3.2.3-0pre6 gcc-snapshot 20030314-1

Bug#186139: gcc-3.2: [alpha] va_start is off by one

2003-03-24 Thread Kalle Olavi Niemitalo
Package: gcc-3.2 Version: 1:3.2.3-0pre6 Severity: normal In the attached program, failing_func should return its first variadic argument, but somehow it returns wrong_value instead. The main function exits with code 0 if the result is correct. I believe this is what causes Debian Bug#185973.

Bug#186139: gcc-3.2: [alpha] va_start is off by one

2003-03-24 Thread Kalle Olavi Niemitalo
Daniel Jacobowitz [EMAIL PROTECTED] writes: Coincidentally, I believe that Falk Hueffner fixed this in the GCC source very recently. Just FYI. You're right, it's PR target/9700.

Bug#185838: blas: FTBFS: CBLAS_IZAMAX test failed on GCC 3.2.3-0pre6

2003-03-22 Thread Kalle Olavi Niemitalo
Package: g77-3.2 Version: 3.2.3-0pre6 Severity: normal I was building blas 1.1-10 from source on i386 with the following packages installed: ii libc6 2.3.1-14 GNU C Library: Shared libraries and Timezone ii libc6-dev 2.3.1-14 GNU C Library: Development Libraries and

Bug#138038: Help offered with report #138038

2003-02-03 Thread Kalle Olavi Niemitalo
reopen 138038 quit The fix in gcc-defaults 1.3 does not work: bash-2.05b# find /usr -name *c++filt* -print0 | xargs -0 ls -ld -rwxr-xr-x1 root root30028 1998-12-04 06:05 /usr/bin/c++filt -rwxr-xr-x1 root root62408 2002-12-05 00:58 /usr/bin/c++filt.binutils

Bug#138038: Help offered with report #138038

2002-12-28 Thread Kalle Olavi Niemitalo
Matthias Klose [EMAIL PROTECTED] writes: please could you run the following commnds: bash-2.05b# sh -x sh-2.05b# dpkg-divert --list c++filt + dpkg-divert --list c++filt sh-2.05b# dpkg-divert --list /usr/bin/c++filt + dpkg-divert --list /usr/bin/c++filt diversion of /usr/bin/c++filt to

Bug#138038: g++: old diversion of c++filt?

2002-09-05 Thread Kalle Olavi Niemitalo
I have the same diversion in my computer. [EMAIL PROTECTED]:~$ ls -l /usr/bin/c++filt* -rwxr-xr-x1 root root30028 1998-12-04 06:05 /usr/bin/c++filt -rwxr-xr-x1 root root55860 2002-08-24 10:50 /usr/bin/c++filt.binutils [EMAIL PROTECTED]:~$ /usr/bin/c++filt