summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2018-10-05 21:54:58 +0000
committerVedant Kumar <vsk@apple.com>2018-10-05 21:54:58 +0000
commit0fea2f5c00d5b9c7fad7fe75fa808be5c5a54fa7 (patch)
treedd7be917fe4a34d1ab0e03531ae061a023e3a360
parent49bf370a8b38a9fde6979fb4be71c06c61671014 (diff)
downloadbcm5719-llvm-0fea2f5c00d5b9c7fad7fe75fa808be5c5a54fa7.tar.gz
bcm5719-llvm-0fea2f5c00d5b9c7fad7fe75fa808be5c5a54fa7.zip
Specify -mtriple=x86_64 in an X86-specific dwarf test
On the PPC bot, the %llc_dwarf substitution does not contain an -mtriple argument. This can cause the wrong backend to be exercised. This causes issues because the backends differ in when they decide to emit tail calls: http://lab.llvm.org:8011/builders/clang-ppc64be-linux-multistage/builds/12440 This is mostly a speculative fix as I don't have a PPC machine to test with. llvm-svn: 343893
-rw-r--r--llvm/test/DebugInfo/X86/dwarf-callsite-related-attrs.ll4
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/test/DebugInfo/X86/dwarf-callsite-related-attrs.ll b/llvm/test/DebugInfo/X86/dwarf-callsite-related-attrs.ll
index 649eb36e26e..f17cd0befdc 100644
--- a/llvm/test/DebugInfo/X86/dwarf-callsite-related-attrs.ll
+++ b/llvm/test/DebugInfo/X86/dwarf-callsite-related-attrs.ll
@@ -13,8 +13,8 @@
; UNSUPPORTED: cygwin,windows-gnu,windows-msvc
; REQUIRES: object-emission
-; RUN: %llc_dwarf < %s -o - | FileCheck %s -check-prefix=ASM
-; RUN: %llc_dwarf < %s -filetype=obj -o %t.o
+; RUN: %llc_dwarf -mtriple=x86_64-- < %s -o - | FileCheck %s -check-prefix=ASM
+; RUN: %llc_dwarf -mtriple=x86_64-- < %s -filetype=obj -o %t.o
; RUN: llvm-dwarfdump %t.o -o - | FileCheck %s -check-prefix=OBJ -implicit-check-not=DW_TAG_call_site
; RUN: llvm-dwarfdump -verify %t.o 2>&1 | FileCheck %s -check-prefix=VERIFY
; RUN: llvm-dwarfdump -statistics %t.o | FileCheck %s -check-prefix=STATS
OpenPOWER on IntegriCloud