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).


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@120164 91177308-0d34-0410-b5e6-96231b3b80d8

test/FrontendObjC++/2007-10-03-MetadataPointers.mm

@@ -1,4 +1,4 @@
-// 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() {

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.

test/FrontendObjC++/2010-08-04-Template.mm

@@ -1,4 +1,4 @@
-// RUN: %llvmgcc %s -S -emit-llvm
+// RUN: %llvmgcc %s -S
 struct TRunSoon {
   template <class P1> static void Post() {}
 };

test/FrontendObjC++/2010-08-06-X.Y-syntax.mm

@@ -1,4 +1,4 @@
-// RUN: %llvmgcc %s -S -emit-llvm
+// RUN: %llvmgcc %s -S
 struct TFENode {
   TFENode(const TFENode& inNode);
 };