Comment 6 for bug 721531

Revision history for this message
Paul Larson (pwlars) wrote :

Not sure if this is relevant, but I seem to be seeing something slightly different. I also added a printf to see what it thinks the value of p is, and tested this with gcc-4.3, 4.4, 4.5:

gcc version 4.3.5 (Ubuntu 4.3.5-3ubuntu1)
without -O2:
p=0x83e0
with -O2:
p=0x83e0

gcc version 4.4.5 (Ubuntu/Linaro 4.4.5-11ubuntu1)
without -O2:
HIT!
p=0x83c1
with -O2:
HIT!
p=0x83c5

gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu1)
without -O2:
HIT!
p=0x83c1
with -O2:
p=0x8399

gcc-4.3 was the only consistent one, but it did not have -mthumb enabled by default.
with gcc-4.3 -mthumb, I get the same thing with or without using -O2:
HIT!
p=0x83e1