Add target triple info to these tests to make the results comparable when

hosted on different platforms.

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

diff --git a/test/DebugInfo/2009-10-16-Scope.ll b/test/DebugInfo/2009-10-16-Scope.ll
index 9f9fa65d5b79d2885b59dddbf1d8147763cb2274..037294fc63a41513cd4ddb747b315d34915f7c62 100644 (file)
--- a/test/DebugInfo/2009-10-16-Scope.ll
+++ b/test/DebugInfo/2009-10-16-Scope.ll
@@ -1,4 +1,5 @@
-; RUN: llc %s -O0 -o /dev/null
+; RUN: llc %s -O0 -o /dev/null -mtriple=x86_64-apple-darwin
+; RUN: llc %s -O0 -o /dev/null -mtriple=arm-apple-darwin
 ; PR 5197
 ; There is not any llvm instruction assocated with !5. The code generator
 ; should be able to handle this.

diff --git a/test/DebugInfo/2010-08-04-StackVariable.ll b/test/DebugInfo/2010-08-04-StackVariable.ll
index 61cd20bb1ab3db2cb3309a50a2faa185e9dff9c3..c35c3d36d261d91b89f97dba068ab176ab9080ba 100644 (file)
--- a/test/DebugInfo/2010-08-04-StackVariable.ll
+++ b/test/DebugInfo/2010-08-04-StackVariable.ll
@@ -1,4 +1,5 @@
-; RUN: llc -O0 < %s | grep DW_OP_fbreg
+; RUN: llc -O0 -mtriple=arm-apple-darwin < %s | grep DW_OP_fbreg
+; RUN: llc -O0 -mtriple=x86_64-apple-darwin < %s | grep DW_OP_fbreg
 ; Use DW_OP_fbreg in variable's location expression if the variable is in a stack slot.
 
 %struct.SVal = type { i8*, i32 }