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 a26ef7e2d2e395b920ae654030d8dbeca1f07378..f1f06210db4a5885179d91b6470377644e243fd3 100644 (file)
--- 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 97f49ef8c432f78968cf066287d4d760d5fdeb23..5de5105644d62eb65dfe11d5b0bf48122457efd5 100644 (file)
--- 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