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
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
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');
... I just forgot about this bug report of mine, however, the problem doesn't
show up anymore on current testing versions, so please close my bug
report. :)
lg
Erik
pgpwCboI5Pvcz.pgp
Description: PGP signature
> Is it the first time you use lineak-xosdplugin, or have you use it
before and it stopped to work?
Well, I used it, and it worked for a while. I pushed the
next-prev-buttons on my girlfriend's multimedia keyboard, and the
messages appeared in amarok. It stopped working months or weeks ago,
Package: lineak-xosdpluginVersion: 1:0.8.3-6Severity: graveJustification: renders package unusableTags: patchHilineak-xosdplugin doesn't print its onscreen messages. The problem seems to be in the initialize_display function inxosd_plugin/xosdplugin.cpp, which is commented out.When I use the follow
6 matches
Mail list logo
