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.
19 lines
616 B
LLVM
19 lines
616 B
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 | %ptxas-verify %}
|
|
|
|
target triple = "nvptx-unknown-cuda"
|
|
|
|
; CHECK: .visible .func foo
|
|
define void @foo(<8 x i8> %a, ptr %b) {
|
|
; CHECK-DAG: ld.param.v2.u32 {[[E0:%r[0-9]+]], [[E1:%r[0-9]+]]}, [foo_param_0]
|
|
; CHECK-DAG: ld.param.u64 %[[B:rd[0-9+]]], [foo_param_1]
|
|
; CHECK: add.s16 [[T:%rs[0-9+]]],
|
|
; CHECK: st.u8 [%[[B]]], [[T]];
|
|
%t0 = extractelement <8 x i8> %a, i32 1
|
|
%t1 = extractelement <8 x i8> %a, i32 6
|
|
%t = add i8 %t0, %t1
|
|
store i8 %t, ptr %b
|
|
ret void
|
|
}
|
|
|