Comment #2 on issue 2514 by [email protected]: Patch: gcc 4.6.3 does not need -fno-optimize-sibling-calls any more
http://code.google.com/p/lilypond/issues/detail?id=2514
Actually, regarding the testing with gcc-4.6.2 or earlier: I don't think a Patchy run would trigger the bug since Patchy switches off optimization. So one should really check the generated compiler options.
