b279f6b098
Similar to 806761a7629df268c8aed49657aeccffa6bca449
-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.
33 lines
758 B
LLVM
33 lines
758 B
LLVM
; RUN: llc < %s -mtriple=nvptx -mcpu=sm_20 | FileCheck %s
|
|
; RUN: llc < %s -mtriple=nvptx64 -mcpu=sm_20 | FileCheck %s
|
|
; RUN: %if ptxas && !ptxas-12.0 %{ llc < %s -mtriple=nvptx -mcpu=sm_20 | %ptxas-verify %}
|
|
; RUN: %if ptxas %{ llc < %s -mtriple=nvptx64 -mcpu=sm_20 | %ptxas-verify %}
|
|
|
|
|
|
;; Kernel function using ptx_kernel calling conv
|
|
|
|
; CHECK: .entry kernel_func
|
|
define ptx_kernel void @kernel_func(ptr %a) {
|
|
; CHECK: ret
|
|
ret void
|
|
}
|
|
|
|
;; Device function
|
|
; CHECK: .func device_func
|
|
define void @device_func(ptr %a) {
|
|
; CHECK: ret
|
|
ret void
|
|
}
|
|
|
|
;; Kernel function using NVVM metadata
|
|
; CHECK: .entry metadata_kernel
|
|
define void @metadata_kernel(ptr %a) {
|
|
; CHECK: ret
|
|
ret void
|
|
}
|
|
|
|
|
|
!nvvm.annotations = !{!1}
|
|
|
|
!1 = !{ptr @metadata_kernel, !"kernel", i32 1}
|