delorie.com/archives/browse.cgi | search |
> Date: Tue, 30 Jun 2009 23:21:31 -0400 > From: DJ Delorie <dj AT delorie DOT com> > > > > Code that's too optimized is a pain to debug. I'm unwilling to > > trade the ability to debug reasonably optimized code for another > > 6.5% of speedup. > > One of the current projects is to improve the ability to debug > optimized code. Yes, I know. I'm waiting impatiently to see such features in a future version of GCC. I miss the days of GCC 2.7.x and 2.8.x, when I could debug a -O2 optimized program with almost the same ease as a non-optimized one. Being able to do that was once one of the most attractive features of GCC among the other C compilers. Now I always compile Emacs with -O1 because otherwise you cannot even get a correct backtrace or put a breakpoint on a static function and know that it will be hit if the function is called.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |