------- Comment #5 from r0bertz at gentoo dot org 2008-11-13 17:27 ------- I am trying to find which specific flag or flags when used together with -foptimize-sibling-calls could trigger this problem. As the first step I tried to find a set of flags used together with -O0 and -foptimize-sibling-calls could trigger this problem. Presumably this set of flags should be those disabled at -O0 but enabled at -O1.
So I did the following to find the differences: gcc -c -Q -O0 --help=optimizers > /tmp/O0-opts gcc -c -Q -O1 --help=optimizers > /tmp/O1-opts diff /tmp/O0-opts /tmp/O1-opts | grep enabled | cut -d " " -f 4 Then I used these flags with -O0 and -foptimize-sibling-calls together, but this didn't trigger the bug. Is there anything I have overlooked here? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38052
