From: Weimin Pan Date: Sat, 11 Feb 2023 00:00:50 +0000 (-0800) Subject: testsuite: sframebt: Use -fno-optimize-sibling-calls X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ed7b28948ee805dac7ba00eeab7e149a1f923970;p=thirdparty%2Fbinutils-gdb.git testsuite: sframebt: Use -fno-optimize-sibling-calls With -O2 and above, the compiler performs a sibling call optimization as main () and it's callee have compatible stack usage. As for generating stack traces though, there is nothing that any stack trace or unwind format can do here. Use -fno-optimize-sibling-calls to at least ensure the testcase checkes for the complete stack trace. ChangeLog: * libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-1.lk: Use -fno-optimize-sibling-calls. * libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-2.lk: Likewise. --- diff --git a/libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-1.lk b/libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-1.lk index a26ef7e2d2e..f1f06210db4 100644 --- a/libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-1.lk +++ b/libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-1.lk @@ -1,4 +1,4 @@ # source: backtrace-fp-attr-1.c -# cflags: -fno-omit-frame-pointer +# cflags: -fno-omit-frame-pointer -fno-optimize-sibling-calls # link: on PASS: backtrace with omit-frame-pointer attr diff --git a/libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-2.lk b/libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-2.lk index 97f49ef8c43..5de5105644d 100644 --- a/libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-2.lk +++ b/libsframe/testsuite/libsframe.unwind/backtrace-fp-attr-2.lk @@ -1,4 +1,4 @@ # source: backtrace-fp-attr-2.c -# cflags: -fomit-frame-pointer +# cflags: -fomit-frame-pointer -fno-optimize-sibling-calls # link: on PASS: backtrace with no-omit-frame-pointer attr