
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.
16 lines
587 B
LLVM
16 lines
587 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-i64:64-i128:128-v16:16-v32:32-n16:32:64"
|
|
target triple = "nvptx-nvidia-cuda"
|
|
|
|
@global_cst = private constant [6 x i1] [i1 true, i1 false, i1 true, i1 false, i1 true, i1 false]
|
|
|
|
; CHECK: .global .align 1 .b8 global_cst[6] = {1, 0, 1, 0, 1}
|
|
define ptx_kernel void @kernel(i32 %i, ptr %out) {
|
|
%5 = getelementptr inbounds i1, ptr @global_cst, i32 %i
|
|
%6 = load i1, ptr %5, align 1
|
|
store i1 %6, ptr %out, align 1
|
|
ret void
|
|
}
|