Hi, Uh ... What does your gut tell you about whether this could be a compiler bug? I could look for that till our sun burns out and probably not find it (I don't know what this computers life expectancy is - but it probably won't last that long). I'm a little more confident about finding something wrong in mesh.c? For the record I've bumped into two files (mesh.c from the Linux kernel and nsUnknownDecoder.cpp from Firefox 2.0.0.15pre) that won't run with 4.3.5. I think nsUnknownDecoder.cpp is ok with -O1. Both Linux and Firefox are pretty big programs. kevin On Wed, Feb 2, 2011 at 6:13 PM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > > That doesn't suggest anything to me and actually it's rather surprising. > -O2 is much more aggressive than -O1 when it comes to breaking code > which superficially looks like it should work. When code breaks with > -O1 it usually means that the code is obviously broken. Or, of course, > there could be a compiler bug. > > Sorry I can't of much help here. What you are asking seems to be a > reasonable question but unfortunately the gcc release process doesn't > work in a way that makes it possible to answer it. > > Ian >
