On 4/5/2012 8:06 AM, Vincent Lefevre wrote:
On 2012-04-05 06:26:43 -0400, Robert Dewar wrote:
Well a lot of users have been burned by using optimization
options, either becausae of compiler bugs, or because of bugs
in their own code triggered by optimization. So the requirement
of not using any optimization options is not that uncommon.
But no-optimizations (-O0) should not necessarily be the default
for these reasons.
I think it is a problem that even at -O1 the debugger is
seriously limited, especially for an inexperienced user.
What is missing to me is a reasonable cleanup of the code that
would remove some of the junk at -O0 but not impact debugging.
In fact a reasonable criterion would be all the optimization
that is cheap to do and does not affect debugging.
Then I would make THAT the default (or simply redefine -O0
to be this level, I see no real advantage in -O0 as it is now)
