http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51323
--- Comment #9 from David Kastrup <dak at gnu dot org> 2011-11-29 11:13:21 UTC --- Code review is at <URL:http://codereview.appspot.com/5431088>, the discussion of the bug is at <URL:http://code.google.com/p/lilypond/issues/detail?id=1997>. As you can see, the proposed workaround is restricted to g++ versions of 4.6.x. I trust that it will be fixed by the time 4.7 gets released, and once we have conclusive evidence about versions of 4.6.x that are unaffected, those will likely not get the fix either. As a suggestion: it might be sensible to have a meta option -fdebug that will disable all options significantly interfering with post mortem debugging. While -g by itself should not change code generation, having a supporting option that helps debugging might be nice. The option set I currently think of is something like -fno-crossjumping -fkeep-inline-functions -fno-optimize-sibling-calls. Also optimization of noreturn functions, in particular of abort, would be disabled since clobbering the stack traceback is not really helpful for debugging. But that's a different issue.
