From 0d7f89d1ac148f105adddafe3ad4e9e4102b220e Mon Sep 17 00:00:00 2001 From: Bill Seurer Date: Fri, 20 Nov 2015 20:47:34 +0000 Subject: [PATCH] Fix test case function name checks This is similar to the earlier fix I did, r253702, expect that here it is function names that are being searched for. If the function name matches part of the directory name it can cause an apparent test case failure. llvm-svn: 253706 --- clang/test/CodeGen/captured-statements.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/clang/test/CodeGen/captured-statements.c b/clang/test/CodeGen/captured-statements.c index 53632ac45d72..607ec8e55f48 100644 --- a/clang/test/CodeGen/captured-statements.c +++ b/clang/test/CodeGen/captured-statements.c @@ -21,7 +21,7 @@ void test1() { // CHECK-1: %struct.anon = type { i32* } // CHECK-1: {{.+}} global float 3.0 // - // CHECK-1: test1 + // CHECK-1: @test1( // CHECK-1: alloca %struct.anon // CHECK-1: getelementptr inbounds %struct.anon, %struct.anon* // CHECK-1: store i32* %i @@ -43,7 +43,7 @@ void test2(int x) { for (i = 0; i < x; i++) foo(); } - // CHECK-2: test2 + // CHECK-2: @test2( // CHECK-2-NOT: %i // CHECK-2: call void @[[HelperName:__captured_stmt[\.0-9]+]] } @@ -60,7 +60,7 @@ void test3(int size) { { arr[2] = vla_arr[size - 1]; } - // CHECK-3: test3 + // CHECK-3: @test3( // CHECK-3: alloca [5 x i32] // CHECK-3: call void @__captured_stmt }