4583f6d344
the `ptx_kernel` calling convention is a more idiomatic and standard way of specifying a NVPTX kernel than using the metadata which is not supposed to change the meaning of the program. Further, checking the calling convention is significantly faster than traversing the metadata, improving compile time. This change updates the clang and mlir frontends as well as the NVPTXCtorDtorLowering pass to emit kernels using the calling convention. In addition, this updates all NVPTX unit tests to use the calling convention as well.
17 lines
616 B
LLVM
17 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 datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v32:32:32-v64:64:64-v128:128:128-n16:32:64"
|
|
target triple = "nvptx-nvidia-cuda"
|
|
|
|
; Make sure predicate (i1) operands to kernels get expanded out to .u8
|
|
|
|
; CHECK: .entry foo
|
|
; CHECK: .param .u8 foo_param_0
|
|
; CHECK: .param .u64 .ptr .align 1 foo_param_1
|
|
define ptx_kernel void @foo(i1 %p, ptr %out) {
|
|
%val = zext i1 %p to i32
|
|
store i32 %val, ptr %out
|
|
ret void
|
|
}
|