Re: --enable-debug does not work with gcc

>> If we did what you suggest, then --enable-debug would cause performance
>> degradation, which would cause people to not use it, which would result
>> in most binaries being completely undebuggable rather than only partially.
>> Doesn't sound like a good tradeoff to me.
>>
>> Personally, in my development tree I use a Makefile.custom containing
>>
>> # back off optimization unless profiling
>> ifeq ($(PROFILE),)
>>    CFLAGS:= $(patsubst -O2,-O1,$(CFLAGS))
>> endif
>>
>> -O1 still generates "uninitialized variable" warnings but the code is a
>> lot saner to step through ... not perfect, but saner.  It's been a
>> workable compromise for a long time.  I don't recommend developing with
>> -O0, exactly because it disables some mighty valuable warnings.
> 
> Agreed.  I use -O1 by default myself, unless I am doing performance testing.
> 
Something for the developers FAQ perhaps? I confess I did not know of
Makefile.custom :-D

//Magnus