On 11/15/2013 09:48 PM, Sieghard wrote: > Not even neccessarily. It could be a programmer error, e.g. such that > he forgot to declare a variable "volatile",
Right. This just hit me some days ago when porting a program from an ancient "MRI" C compiler to a modern gnu compiler. But even here, the Compiler issued a "gimple" error message and declined to compile my source code (because the function was called from within the same source code file, the compiler would not have been able to detect the problem when calling the function from another file.) Unfortunately it was really hard to find out that an erroneous volatile definition was the cause of the nasty "gimple" error. > Optimization can even change the program flow without creating > errors, e.g. by more aggressive inlining of functions - remember, a > function declared "inline" _needs not_ to be always inserted literally > by the compiler. That is true. But source code that is affected by that needs to be regarded as erroneous. -Michael ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
