Bug#372913: gcc-4.1: datatype limits / signedness differs with optimization levels

2006-06-12 Thread Erik Meusel
Am Montag, 12. Juni 2006 18:24 schrieb Bastian Blank: > char is neither signed nor unsigned. Only unsigned have defined overflow > behaviour. > > > } while (c != '\0'); > > > > return 0; > > } Alright, but why does this work differently using different versions of gcc or different

Bug#372913: assembler output...

2006-06-12 Thread Erik Meusel
I made a diff of the assembler code with -O0 and -O2: 1 --- test_O0 2006-06-12 15:30:56.0 +0200 2 +++ test_O2 2006-06-12 15:30:49.0 +0200 3 @@ -1,5 +1,6 @@ 4 .file "test.c" 5 .text 6 + .p2align 4,,15 7 .glob

Bug#372913: gcc-4.1: datatype limits / signedness differs with optimization levels

2006-06-12 Thread Erik Meusel
Package: gcc-4.1 Version: 4.1.1-2 Severity: critical Justification: breaks unrelated software Use this little example to see what's happening: #include int main(void) { char c = '\0'; do { printf("%d\n", c); c++; } while (c != '\0');