Marshall Lake <mlake@xxxxxxxxx> writes: > > That is correct. There is no gcc 4.1.3 release. I don't know what > > code you are using. > > Could it be that 4.1.3 was changed to be the initial release in the > 4.2.x series? And somehow I downloaded an "in-between" version? No, that could not have happened. gcc releases are made from branches. > > If you can't figure out why code is not executing properly, a good > > thing to try is -fno-strict-aliasing. Another is > > -fno-strict-overflow. If either of those options fixes the problem, > > then it is likely that your code is accidentally relying on > > undefined behaviour. > > Neither of those two options fixes the problem for me. Could that > mean that there's a bug in the 4.2.x series? It could. Compiler bugs are much less common than coding bugs, but they do happen. Ian
