Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

[lilypond]

Comment #23 on issue 1997 by address@hidden: segfault in  
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997

The right option for avoiding the bad optimization would appear to be  
-fno-optimize-sibling-calls and, frankly, it is actually insane that  
-fkeep-inline-functions works as well since it is documented as doing  
something completely unrelated to the faulty code generation.

Switching off sibling call optimization will also improve the usefulness of  
stack backtraces for debugging and diagnosis since it does not clobber the  
stack frames of callers that have nothing left to do except return.

I doubt that the we'll even notice the added stack usage since we don't  
really employ the sort of call chaining in C++ where this optimization  
renders noticeable savings.