From 8b6ef88e7eb618dea0160eaddecf901eb28bc2e1 Mon Sep 17 00:00:00 2001 From: Zachary Turner Date: Mon, 20 Nov 2017 21:41:36 +0000 Subject: Resubmit "Refactor debuginfo-tests" again. This was reverted due to the tests being run twice on some build bots. Each run had a slightly different configuration due to the way in which it was being invoked. This fixes the problem (albeit in a somewhat hacky way). Hopefully in the future we can get rid of the workflow of running debuginfo-tests as part of clang, and then this hack can go away. llvm-svn: 318697 --- debuginfo-tests/nested-struct.cpp | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 debuginfo-tests/nested-struct.cpp (limited to 'debuginfo-tests/nested-struct.cpp') diff --git a/debuginfo-tests/nested-struct.cpp b/debuginfo-tests/nested-struct.cpp deleted file mode 100644 index 7533e6a8151..00000000000 --- a/debuginfo-tests/nested-struct.cpp +++ /dev/null @@ -1,21 +0,0 @@ -// RUN: %clangxx %target_itanium_abi_host_triple -O0 -g %s -c -o %t.o -// RUN: %test_debuginfo %s %t.o -// Radar 9440721 -// If debug info for my_number() is emitted outside function foo's scope -// then a debugger may not be able to handle it. At least one version of -// gdb crashes in such cases. - -// DEBUGGER: ptype foo -// CHECK: int (void) - -int foo() { - struct Local { - static int my_number() { - return 42; - } - }; - - int i = 0; - i = Local::my_number(); - return i + 1; -} -- cgit v1.2.3