Hallo Michael, Du schriebst am Fri, 15 Nov 2013 09:10:37 +0100:
> On 11/14/2013 09:49 PM, Sieghard wrote: > > > >> For debugging you can define a lower Optimization level. > > You can d that, of course. Often, then, the reason for debugging goes > > away. > ???? > Optimization levels are only allowed to affect execution speed and code > size. In theory, you're right. > If the result of a function is different with a different optimization > this needs to be seen as a compiler bug. Not even neccessarily. It could be a programmer error, e.g. such that he forgot to declare a variable "volatile", therewith allowing the compiler to optimize some use of it away, leading to unexpected behaviour. 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. -- -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- ------------------------------------------------------------------------------ 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
