Bug#150050: acknowledged by developer (fixed in gcc-2.95.3)

2002-07-23 Thread Martin v. Loewis
[EMAIL PROTECTED] writes: However, as I understand it, the bug indicated a problem with the compiler (an internal error), so other programs compiled with the compiler would fail. That's incorrect. If the compiler encounters an internal error, it refuses to compile. So programs that suffer

Bug#153965: gcc-3.1: incorrect line numbers in warning messages when using inline functions

2002-07-23 Thread Andrew Suffield
Package: gcc-3.1 Version: 1:3.1.1-0pre3 Severity: normal static inline int foo(int x) { if (!x) return 0; } int main(void) { foo(1); return 1; } Building this with gcc-3.1 -c -o foo.o foo.c -Wall gives this output: foo.c: In function `foo': foo.c:13: warning: control reaches end of

Bug#153965: gcc-3.1: incorrect line numbers in warning messages when using inline functions

2002-07-23 Thread Phil Edwards
On Tue, Jul 23, 2002 at 11:04:48AM +0100, Andrew Suffield wrote: Package: gcc-3.1 Version: 1:3.1.1-0pre3 Severity: normal Could you try this with one of the 3.2 compilers, maybe the gcc-snapshot package? I know that there were some weird bugs with line numbers in error messages up until a