On 05/21/2012 05:10 PM, Lubos Lunak wrote:
On Friday 18 of May 2012, Stephan Bergmann wrote:
Ah, you wanted --enable-dbgutil to disable -O2, the same way that
--enable-debug does. Had missed that point. Hm, as I said, I prefer
my --enable-dbgutil --disable-debug builds to be -O2.
What is the point of that combination? As far as I can tell
--enable-dbgutil is like --enable-debug but for changes that are BIC,
so only dbgutil without debug does not make much sense to me.
I rarely use a debugger to step through code, so I prefer to avoid the
--enable-debug settings that, AFAIU, are mainly there to aid in
step-through debugging, but nevertheless cause potential deviation from
a production build (like -O0, -fno-inline).