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.
27 lines
804 B
LLVM
27 lines
804 B
LLVM
; RUN: llc < %s -mtriple=nvptx -mcpu=sm_20 -verify-machineinstrs | FileCheck %s
|
|
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 -verify-machineinstrs | FileCheck %s
|
|
; RUN: %if ptxas && !ptxas-12.0 %{ llc < %s -mtriple=nvptx -mcpu=sm_20 -verify-machineinstrs | %ptxas-verify %}
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 -verify-machineinstrs | %ptxas-verify %}
|
|
|
|
; CHECK: .func ({{.*}}) device_func
|
|
define float @device_func(float %a) noinline {
|
|
%ret = fmul float %a, %a
|
|
ret float %ret
|
|
}
|
|
|
|
; CHECK: .entry kernel_func
|
|
define void @kernel_func(ptr %a) {
|
|
%val = load float, ptr %a
|
|
; CHECK: call.uni (retval0),
|
|
; CHECK: device_func,
|
|
%mul = call float @device_func(float %val)
|
|
store float %mul, ptr %a
|
|
ret void
|
|
}
|
|
|
|
|
|
|
|
!nvvm.annotations = !{!1}
|
|
|
|
!1 = !{ptr @kernel_func, !"kernel", i32 1}
|