From ae674aeaabfd0889fc35dbfb5b65110ceecbc08e Mon Sep 17 00:00:00 2001 From: Matt Arsenault Date: Fri, 3 May 2019 19:04:14 +0000 Subject: [PATCH] Ensure there is stack usage in stack size warning test r359906 broke this because the only stack usage was from a spill which can be avoided since the only block is a return. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@359918 91177308-0d34-0410-b5e6-96231b3b80d8 --- test/Misc/backend-stack-frame-diagnostics-fallback.cpp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/test/Misc/backend-stack-frame-diagnostics-fallback.cpp b/test/Misc/backend-stack-frame-diagnostics-fallback.cpp index 8ae8c55396..332dd22fec 100644 --- a/test/Misc/backend-stack-frame-diagnostics-fallback.cpp +++ b/test/Misc/backend-stack-frame-diagnostics-fallback.cpp @@ -14,5 +14,7 @@ namespace frameSizeThunkWarning { // CHECK: warning: stack frame size of {{[0-9]+}} bytes in function 'frameSizeThunkWarning::B::f' // CHECK: warning: stack size limit exceeded ({{[0-9]+}}) in {{[^ ]+}} - void B::f() { } + void B::f() { + volatile int x = 0; // Ensure there is stack usage. + } } -- 2.50.1