Martin Ward wrote, in part: >But why does the un-optimised code not include the optimisations >that the optimised code has? Well, compiling is always >a trade-off between compile time and execution time. >By turning off optimisation the programmer has declared >that compile time is the most important factor: so the compiler >will parse the source and generate some kind of working code >as quickly as possible, without worrying about the execution >time of the generated code. If you want better code, >and you are prepared to spend more time waiting for it to >be produced, then simply turn on optimisation!
Again--and I feel like I'm being argumentative here, but I don't mean to be--I can buy that for cross-statement optimization. But for the statement in question: int var = 0; -- to produce such horrendous code still makes me wonder.
