b279f6b098
Similar to 806761a762
-mtriple= specifies the full target triple while -march= merely sets the
architecture part of the default target triple (e.g. Windows, macOS),
leaving a target triple which may not make sense.
Therefore, -march= is error-prone and not recommended for tests without
a target triple. The issue has been benign as we recognize
nvptx{,64}-apple-darwin as ELF instead of rejecting it outrightly.
15 lines
548 B
LLVM
15 lines
548 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 | %ptxas-verify %}
|
|
|
|
declare <4 x float> @bar()
|
|
|
|
; CHECK-LABEL: .func foo(
|
|
define void @foo(ptr %ptr) {
|
|
; CHECK: ld.param.u64 %[[PTR:rd[0-9]+]], [foo_param_0];
|
|
; CHECK: ld.param.v4.f32 {[[E0:%f[0-9]+]], [[E1:%f[0-9]+]], [[E2:%f[0-9]+]], [[E3:%f[0-9]+]]}, [retval0];
|
|
; CHECK: st.v4.f32 [%[[PTR]]], {[[E0]], [[E1]], [[E2]], [[E3]]}
|
|
%val = tail call <4 x float> @bar()
|
|
store <4 x float> %val, ptr %ptr
|
|
ret void
|
|
}
|