From 13cf19dff098bf89216a14eee0314afd850278a2 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. llvm-svn: 359918 --- clang/test/Misc/backend-stack-frame-diagnostics-fallback.cpp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/clang/test/Misc/backend-stack-frame-diagnostics-fallback.cpp b/clang/test/Misc/backend-stack-frame-diagnostics-fallback.cpp index 8ae8c55396dc..332dd22fecb3 100644 --- a/clang/test/Misc/backend-stack-frame-diagnostics-fallback.cpp +++ b/clang/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. + } }