Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[NVPTX] Enhance vectorization of ld.param & st.param
Since function parameters and return values are passed via param space, we can force special alignment for values hold in it which will add vectorization options. This change may be done if the function has private or internal linkage. Special alignment is forced during 2 phases. 1) Instruction selection lowering. Here we use special alignment for function prototypes (changing both own return value and parameters alignment), call lowering (changing both callee's return value and parameters alignment). 2) IR pass nvptx-lower-args. Here we change alignment of byval parameters that belong to param space (or are casted to it). We only handle cases when all uses of such parameters are loads from it. For such loads, we can change the alignment according to special type alignment and the load offset. Then, load-store-vectorizer IR pass will perform vectorization where alignment allows it. Special alignment calculated as maximum from default ABI type alignment and alignment 16. Alignment 16 is chosen because it's the maximum size of vectorized ld.param & st.param. Before specifying such special alignment, we should check if it is a multiple of the alignment that the type already has. For example, if a value has an enforced alignment of 64, default ABI alignment of 4 and special alignment of 16, we should preserve 64. This patch will be followed by a refactoring patch that removes duplicating code in handling byval and non-byval arguments. Differential Revision: https://reviews.llvm.org/D121549
- Loading branch information
Showing
7 changed files
with
1,544 additions
and
55 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,32 @@ | ||
// RUN: %clang_cc1 -triple nvptx -fcuda-is-device \ | ||
// RUN: -emit-llvm -o - %s \ | ||
// RUN: %clang_cc1 -triple nvptx -fcuda-is-device -emit-llvm -o - %s \ | ||
// RUN: | FileCheck -check-prefix=NORDC %s | ||
// RUN: %clang_cc1 -triple nvptx -fcuda-is-device \ | ||
// RUN: -fgpu-rdc -emit-llvm -o - %s \ | ||
// RUN: %clang_cc1 -triple nvptx -fcuda-is-device -emit-llvm -o - %s \ | ||
// RUN: | FileCheck -check-prefix=NORDC-NEG %s | ||
// RUN: %clang_cc1 -triple nvptx -fcuda-is-device -fgpu-rdc -emit-llvm -o - %s \ | ||
// RUN: | FileCheck -check-prefix=RDC %s | ||
// RUN: %clang_cc1 -triple nvptx -fcuda-is-device -fgpu-rdc -emit-llvm -o - %s \ | ||
// RUN: | FileCheck -check-prefix=RDC-NEG %s | ||
|
||
#include "Inputs/cuda.h" | ||
|
||
// NORDC: define internal void @_Z4funcIiEvv() | ||
// NORDC: define{{.*}} void @_Z6kernelIiEvv() | ||
// RDC: define weak_odr void @_Z4funcIiEvv() | ||
// RDC: define weak_odr void @_Z6kernelIiEvv() | ||
|
||
template <typename T> __device__ void func() {} | ||
template <typename T> __global__ void kernel() {} | ||
|
||
template __device__ void func<int>(); | ||
// NORDC: define internal void @_Z4funcIiEvv() | ||
// RDC: define weak_odr void @_Z4funcIiEvv() | ||
|
||
template __global__ void kernel<int>(); | ||
// NORDC: define void @_Z6kernelIiEvv() | ||
// RDC: define weak_odr void @_Z6kernelIiEvv() | ||
|
||
// Ensure that unused static device function is eliminated | ||
static __device__ void static_func() {} | ||
// NORDC-NEG-NOT: define{{.*}} void @_ZL13static_funcv() | ||
// RDC-NEG-NOT: define{{.*}} void @_ZL13static_funcv() | ||
|
||
// Ensure that kernel function has external or weak_odr | ||
// linkage regardless static specifier | ||
static __global__ void static_kernel() {} | ||
// NORDC: define void @_ZL13static_kernelv() | ||
// RDC: define weak_odr void @_ZL13static_kernelv() |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.