automatically. Use -S with llvm-gcc rather than -c, so tests can
work when llvm-gcc is really dragonegg (which can output IR with -S
but not -c). Yes, dragonegg supports objective-c++ (poorly though).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@120164
91177308-0d34-0410-b5e6-
96231b3b80d8
-// RUN: %llvmgcc -w -x objective-c++ -c %s -o /dev/null
+// RUN: %llvmgcc -w -x objective-c++ -S %s -o /dev/null
@class NSImage;
void bork() {
-// RUN: not %llvmgcc %s -S -emit-llvm -o - |& FileCheck %s
+// RUN: not %llvmgcc %s -S -o - |& FileCheck %s
// This tests for a specific diagnostic in LLVM-GCC.
// Clang compiles this correctly with no diagnostic,
// ergo this test will fail with a Clang-based front-end.
-// RUN: %llvmgcc %s -S -emit-llvm
+// RUN: %llvmgcc %s -S
struct TRunSoon {
template <class P1> static void Post() {}
};
-// RUN: %llvmgcc %s -S -emit-llvm
+// RUN: %llvmgcc %s -S
struct TFENode {
TFENode(const TFENode& inNode);
};