Remove explicit uses of -emit-llvm, the test infrastructure adds it
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).
llvm-svn: 120164
diff --git a/llvm/test/FrontendObjC++/2010-08-02-NonPODObjectValue.mm b/llvm/test/FrontendObjC++/2010-08-02-NonPODObjectValue.mm
index 298844e..da47ed0 100644
--- a/llvm/test/FrontendObjC++/2010-08-02-NonPODObjectValue.mm
+++ b/llvm/test/FrontendObjC++/2010-08-02-NonPODObjectValue.mm
@@ -1,4 +1,4 @@
-// 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.