29a5c3c8fe
We may want to be able to mark certain regions as kernels even without being in an accepted CUDA or OpenCL language mode. This patch introduces a new attribute limited to `nvptx` targets called `nvptx_kernel` which will perform the same metadata action as the existing CUDA ones. This closely mimics the behaviour of the `amdgpu_kernel` attribute. This allows for making executable NVPTX device images without using an existing offloading language model. I was unsure how to do this, I could potentially re-use all the CUDA attributes and just replace the `CUDA` language requirement with an `NVPTX` architecture requirement. Also I don't know if I should add more than just this attribute. Reviewed By: tra Differential Revision: https://reviews.llvm.org/D140226
18 lines
797 B
C
18 lines
797 B
C
// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py UTC_ARGS: --function-signature --check-attributes --check-globals
|
|
// RUN: %clang_cc1 -triple nvptx64-nvidia-cuda -target-cpu sm_61 -emit-llvm %s -o - | FileCheck %s
|
|
|
|
// CHECK: Function Attrs: noinline nounwind optnone
|
|
// CHECK-LABEL: define {{[^@]+}}@foo
|
|
// CHECK-SAME: (ptr noundef [[RET:%.*]]) #[[ATTR0:[0-9]+]] {
|
|
// CHECK-NEXT: entry:
|
|
// CHECK-NEXT: [[RET_ADDR:%.*]] = alloca ptr, align 8
|
|
// CHECK-NEXT: store ptr [[RET]], ptr [[RET_ADDR]], align 8
|
|
// CHECK-NEXT: [[TMP0:%.*]] = load ptr, ptr [[RET_ADDR]], align 8
|
|
// CHECK-NEXT: store i32 1, ptr [[TMP0]], align 4
|
|
// CHECK-NEXT: ret void
|
|
__attribute__((nvptx_kernel)) void foo(int *ret) {
|
|
*ret = 1;
|
|
}
|
|
|
|
// CHECK: !0 = !{ptr @foo, !"kernel", i32 1}
|