"" <[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 s
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 n
"" writes:
> Hi,
>
> Thanks for the reply. I realize that as of the recent release of 3.0
> stable, of course, this issue is less important, and as I was compiling
> a program from the previous testing under the previous stable, the
> reported bug was hardly critical.
>
> However, as I understan
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 m
4 matches
Mail list logo
