Bug#805820: -Wuninitialized provokes unexpected error with LTO

2015-11-22 Thread Richard Kettlewell
Package: g++-5 Version: 5.2.1-23 $ type g++-5 g++-5 is /usr/bin/g++-5 $ dpkg -l g++-5 libstdc++-5-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name

Bug#789369: iostream uninitialized data

2015-06-20 Thread Richard Kettlewell
Package: libstdc++6 Version: 5.1.1-11 richard@deodand:~/junk$ cat t.cc #include iostream int main() { std::cout std::hex; return 0; } richard@deodand:~/junk$ clang++-3.6 -fsanitize=undefined -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -g -o t t.cc richard@deodand:~/junk$ ./t

Bug#751812: Incorrect fortify warning with -flto

2014-06-16 Thread Richard Kettlewell
Package: gcc-4.9 Version: 4.9.0-6 $ cat t.c #define _FORTIFY_SOURCE 2 #include stdio.h #include limits.h long long size; void execute(void) { unsigned char input[4096]; size_t bytes = (size (ssize_t)sizeof input ? sizeof input : size); size_t

Bug#483069: Ghostscript error while running weekly cron job

2010-09-05 Thread Richard Kettlewell
$ pstotext /usr/share/doc/libstdc++6-4.3-doc/libstdc++/html/_form0.ps GPL Ghostscript 8.62: Unrecoverable error, exit code 1 ...specifically it is failing to open _form0.eps, which does not exist. However, _form0.eps.gz does exist. $ pwd /usr/share/doc/libstdc++6-4.3-doc/libstdc++/html $

Bug#580496: Apparently depends on nonexistent gcc-4.4-doc

2010-06-18 Thread Richard Kettlewell
Vincent Lefevre wrote: I have no problems with: [..] This bug should probably be closed (or reassigned, if the problem is with some sources). Evidently someone has uploaded gcc-4.4-doc since I reported the bug l-) I agree that the bug can be closed. ttfn/rjk -- To UNSUBSCRIBE, email

Bug#526620: Submitted upstream

2010-06-13 Thread Richard Kettlewell
I've submitted this upstream (having found that it exists in GCC 4.5.0 too). http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44511 ttfn/rjk -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#580496: Apparently depends on nonexistent gcc-4.4-doc

2010-05-06 Thread Richard Kettlewell
Package: gcc-doc deodand:~# apt-get install gcc-doc Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some

Bug#526620: closed by Arthur Loiret aloi...@debian.org (reply to aloi...@debian.org) (Re: Bug#526620: False positive from -Wreturn-type)

2009-12-24 Thread Richard Kettlewell
reopen 526620 quit Arthur Loiret wrote: 2009/12/24, Richard Kettlewell r...@terraraq.org.uk: This function's return type is required to be 'void *' because it is passed to pthread_create(); but it never actually returns. However, gcc-4.4 -Wall generates the following warning

Bug#526620: closed by Arthur Loiret aloi...@debian.org (reply to aloi...@debian.org) (Re: Bug#526620: False positive from -Wreturn-type)

2009-12-23 Thread Richard Kettlewell
reopen 526620 quit This function's return type is required to be 'void *' because it is passed to pthread_create(); but it never actually returns. However, gcc-4.4 -Wall generates the following warning for it: playrtp.c: In function ‘queue_thread’: playrtp.c:327: error: no return statement in

Bug#526620: False positive from -Wreturn-type

2009-05-07 Thread Richard Kettlewell
Hello, Matthias Klose wrote: please could you forward this upstream, and add the upstream link to the report? I was slightly surprised to receive this reply as the bug reporting instructions explicitly said I shouldn't do that: Don't file bugs upstream If you file a bug in Debian,

Bug#526620: False positive from -Wreturn-type

2009-05-02 Thread Richard Kettlewell
Package: gcc-4.4 Version: 4.4.0-1 I have the following code: static void *queue_thread(void attribute((unused)) *arg) { struct packet *p; for(;;) { /* Get the next packet */ pthread_mutex_lock(receive_lock); while(!received_packets) { pthread_cond_wait(receive_cond,

Bug#354700: gcc 4 does not notice C syntax error

2006-02-28 Thread Richard Kettlewell
Package: gcc Version: 4.0.2-5 This is what happens if you accidentally put a stray semicolon in a parameter-type-list: [EMAIL PROTECTED]:~$ cat t.c int foo(int x;) { } [EMAIL PROTECTED]:~$ gcc-4.0 --version gcc-4.0 (GCC) 4.0.3 20051201 (prerelease) (Debian 4.0.2-5) Copyright (C) 2005

Bug#46550: #46550 has re-appeared

2003-06-08 Thread Richard Kettlewell
reopen 46550 stop This bug has reappeared at some point in the intervening years (in libstdc++2.10-dev 2.95.4-11woody now). Here's a patch to /usr/include/g++-3/std/bastring.h to put it back right again. ttfn/rjk --- bastring.h.orig Sun Jun 8 22:47:05 2003 +++ bastring.h Sun Jun 8

Bug#46550: #46550 has re-appeared

2003-06-08 Thread Richard Kettlewell
Richard Kettlewell writes: This bug has reappeared at some point in the intervening years (in libstdc++2.10-dev 2.95.4-11woody now). Here's a patch to /usr/include/g++-3/std/bastring.h to put it back right again. ttfn/rjk Sorry, stupid me, it should be:- --- bastring.h.orig Sun Jun

Bug#46550: 3rd time lucky?

2003-06-08 Thread Richard Kettlewell
Maybe I've send the right patch this time; it does at last actually correspond to the version that lets my code build. Apologies for faffing. Under the circumstances you'd better review the patch carefuly though l-) ttfn/rjk --- bastring.h.orig Sun Jun 8 22:47:05 2003 +++ bastring.h Sun