llvm-symbolizer: Extract individual test cases now that it's easier to use directly (without a piped input file)

Pulling out the split-dwarf tests by way of example of how I think
llvm-symbolizer should be tested going forward. Open to
debate/discussion, though.

llvm-svn: 352004

1 files changed, 22 insertions, 0 deletions

diff --git a/llvm/test/tools/llvm-symbolizer/Inputs/split-dwarf-dwp.cpp b/llvm/test/tools/llvm-symbolizer/Inputs/split-dwarf-dwp.cpp
new file mode 100644
index 00000000000..629d8b6aa8f
--- /dev/null
+++ b/llvm/test/tools/llvm-symbolizer/Inputs/split-dwarf-dwp.cpp
@@ -0,0 +1,22 @@
+void f1() {}
+__attribute__((always_inline)) inline void f2() {
+  f1();
+}
+// throw a gap in the address range to force use of DW_AT_ranges, ranges_base,
+// range contribution in the .dwo file, etc.
+__attribute__((nodebug)) void gap() {
+}
+int main() {
+  f2();
+}
+
+// To produce split-dwarf-dwp.o{,dwp}, Create another file that has ranges, so
+// the ranges_base of the CU for split-dwarf-dwp.cpp is non-zero.
+//
+//   $ cat > other.cpp
+//   void other1() {}
+//   __attribute__((nodebug)) void other2() {}
+//   void other3() {}
+//   $ clang++ other.cpp split-dwarf-dwp.cpp -gsplit-dwarf -c -Xclang -fdebug-compilation-dir -Xclang . -fno-split-dwarf-inlining
+//   $ llvm-dwp other.dwo split-dwarf-dwp.dwo -o test/DebugInfo/Inputs/split-dwarf-dwp.o.dwp
+//   $ ld -r other.o split-dwarf-dwp.o -o test/DebugInfo/Inputs/split-dwarf-dwp.o