Helmut Grohne writes ("Bug#766708: Processed: Re: Bug#766708: breaks multiarch
cross building"):
> Since it is my interest to not cause more work on Matthias, I will try
> to summarize his POV.
Thanks.
> The most obvious bug is the one mentioned in the patch: #760770
> It is about a bug in the i
Package: gcc-4.8
Version: 4.8.2-21
Whether various combinations of options imply -Wunused-parameter in
the presence of -Wno-unused depends on where on the command line
-Wno-unused appears:
sid$ cat tt.c
void foo(int x) { }
sid$ gcc -g -O2 -Wall -Wno-unused -W -c tt.c
sid$ gcc -g -O2 -Wall -W -Wn
Package: gcc-4.4
Version: 4.4.5-8
$ /usr/bin/gcc-4.4 -c -pdie-you-bastard -x c /dev/null
gcc-4.4: unrecognized option '-pdie-you-bastard'
$ echo $?
0
$
Ian.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi
Ben Hutchings writes ("Increasing minimum 'i386' processor"):
> The 486-class processors that would no longer be supported are:
> 1. All x86 processors with names including '486'
I'm still running the machine below, and it would be irritating to
have to replace it.
Perhaps a better approach would
Package: gcc-4.3
Version: 4.3.2-1.1
The changelog for gcc-4.3 says:
gcc-4.3 (4.3.1-5) unstable; urgency=low
* Update to SVN 20080705 from the gcc-4_3-branch.
- Fix PR target/36634, wrong-code on powerpc with -msecure-plt.
* Fix PR target/35965, PIC + -fstack-protector on arm/arme
Package: gcc
Version: 4:4.3.2-2
Severity: wishlist
(This wishlist bug report should probably go upstream.)
Consider the following program:
void ha(const char *fmt, ...) __attribute__((format(printf,1,2)));
void haha(const char *fmt, const char *fmt2, ...)
__attribute__((format(printf,
Package: cpp-4.1
Version: 4.1.1-21
mariner:~/junk> cat t.c
#include
int x;
mariner:~/junk> gcc-4.1 -c -MD t.c && echo hi
t.c:1:25: error: nonexistent.h: No such file or directory
mariner:~/junk> gcc-4.1 -c -MMD t.c && echo hi
t.c:1:25: warning: nonexistent.h: No such file or directory
hi
mariner:
I have cloned this bug so that I can reassign this clone to GCC
See the transcript in the original report. We see this:
cc -g -Wall -Wmissing-prototypes -Wstrict-prototypes -Werror -O2
-Wno-pointer-sign -Wno-strict-aliasing -fPIC -I/usr/include/tcl8.4 -I../base
-DTCL_MEM_DEBUG -MMD -o
hoo
Package: gcc-4.1
Version: 4.1.2-9
strace shows what I assume is collect2 trying to write to its fd 2
which I didn't redirect, so presumably the compiler driver did.
I actually found this bug on Ubuntu with 4.1.2-9ubuntu2 but I'd be
very surprised if it isn't also present in the corresponding Debi
Package: gcc
Version: 4:4.0.2-2
Summary:
GCC should be more tolerant of
gcc -Wno-this-is-not-a-recognised-warning
as specified in detail below.
Discussion:
Occasionally, GCC introduces new warnings. For example, GCC 4 has
introduced warnings about discrepancies in signedness of integers
poi
10 matches
Mail list logo
