On Tuesday, 12 February 2013 at 17:29:07 UTC, deadalnix wrote:
On Monday, 11 February 2013 at 18:38:28 UTC, John Colvin wrote:
On Monday, 11 February 2013 at 17:51:30 UTC, deadalnix wrote:
Finally, why would you disable something that make your code
faster ?
in order to do easier debugging / to avoid implementation bugs
This is where the difference between allowing and enforcing
lies.
Of course, but it's always nice to be able to disable any
optimization globally for any given compilation.
I personally like gcc's approach where you have very fine grained
control over all optimisations. Something like this should have a
compiler switch to enable/disable.
