Generally one can observe many bugs after release of a new gcc on, for example Debian or Gentoo bugzilla (gcc bugzilla is a nice place too ;) ). Most of them are program bugs (non-strict aliasing etc.) but there are gcc as well.
]]>To be completely sure, you have to replace every “;” with a “;” in your whole project, and do a full compile!
And yes, its not a typo that there are two “;” :-)
]]>My guess would be that the problem lies in the optimization of the compiler which sometimes does not what the programmer wanted…
]]>I find archaic the compiling errors that being detected outright allow to make correct code directly.
Long life to type-less and interpreted languages.
]]>