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.
36 lines
1.2 KiB
LLVM
36 lines
1.2 KiB
LLVM
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 | FileCheck %s
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 | %ptxas-verify %}
|
|
|
|
define float @foo(<2 x float> %a) {
|
|
; CHECK: .func (.param .b32 func_retval0) foo
|
|
; CHECK: .param .align 8 .b8 foo_param_0[8]
|
|
; CHECK: ld.param.v2.f32 {%f{{[0-9]+}}, %f{{[0-9]+}}}
|
|
%t1 = fmul <2 x float> %a, %a
|
|
%t2 = extractelement <2 x float> %t1, i32 0
|
|
%t3 = extractelement <2 x float> %t1, i32 1
|
|
%t4 = fadd float %t2, %t3
|
|
ret float %t4
|
|
}
|
|
|
|
|
|
define float @bar(<4 x float> %a) {
|
|
; CHECK: .func (.param .b32 func_retval0) bar
|
|
; CHECK: .param .align 16 .b8 bar_param_0[16]
|
|
; CHECK: ld.param.v4.f32 {%f{{[0-9]+}}, %f{{[0-9]+}}, %f{{[0-9]+}}, %f{{[0-9]+}}}
|
|
%t1 = fmul <4 x float> %a, %a
|
|
%t2 = extractelement <4 x float> %t1, i32 0
|
|
%t3 = extractelement <4 x float> %t1, i32 1
|
|
%t4 = fadd float %t2, %t3
|
|
ret float %t4
|
|
}
|
|
|
|
|
|
define <4 x float> @baz(<4 x float> %a) {
|
|
; CHECK: .func (.param .align 16 .b8 func_retval0[16]) baz
|
|
; CHECK: .param .align 16 .b8 baz_param_0[16]
|
|
; CHECK: ld.param.v4.f32 {%f{{[0-9]+}}, %f{{[0-9]+}}, %f{{[0-9]+}}, %f{{[0-9]+}}}
|
|
; CHECK: st.param.v4.f32 [func_retval0], {%f{{[0-9]+}}, %f{{[0-9]+}}, %f{{[0-9]+}}, %f{{[0-9]+}}}
|
|
%t1 = fmul <4 x float> %a, %a
|
|
ret <4 x float> %t1
|
|
}
|