Home
last modified time | relevance | path

Searched refs:kernels (Results 1 – 25 of 134) sorted by relevance

123456

/llvm-project-15.0.7/mlir/test/Conversion/GPUToSPIRV/
H A Dbuiltins.mlir13 gpu.module @kernels {
39 gpu.module @kernels {
63 gpu.module @kernels {
86 gpu.module @kernels {
111 gpu.module @kernels {
133 gpu.module @kernels {
156 gpu.module @kernels {
180 gpu.module @kernels {
197 gpu.module @kernels {
213 gpu.module @kernels {
[all …]
H A Dsimple.mlir4 gpu.module @kernels {
21 gpu.launch_func @kernels::@basic_module_structure
31 gpu.module @kernels {
55 gpu.module @kernels {
67 gpu.launch_func @kernels::@missing_entry_point_abi
77 gpu.module @kernels {
94 gpu.module @kernels {
111 gpu.module @kernels {
125 gpu.launch_func @kernels::@barrier
H A Dmodule-structure-opencl.mlir7 gpu.module @kernels {
25 gpu.launch_func @kernels::@basic_module_structure
/llvm-project-15.0.7/mlir/test/Dialect/GPU/
H A Dasync-region.mlir6 gpu.module @kernels {
16 gpu.launch_func @kernels::@kernel
19 gpu.launch_func @kernels::@kernel
36 gpu.launch_func @kernels::@kernel
47 gpu.launch_func @kernels::@kernel
66 gpu.launch_func @kernels::@kernel
84 gpu.launch_func @kernels::@kernel
112 gpu.launch_func @kernels::@kernel
134 gpu.launch_func @kernels::@kernel
148 gpu.launch_func @kernels::@kernel
[all …]
H A Dinvalid.mlir80 // expected-error@+1 {{kernel module 'kernels' is undefined}}
89 module @kernels {
100 module @kernels {
104 // expected-error@+1 {{kernel module 'kernels' is undefined}}
113 gpu.module @kernels { }
125 gpu.module @kernels {
140 module @kernels {
147 // expected-error@+1 {{kernel module 'kernels' is undefined}}
156 gpu.module @kernels {
172 gpu.module @kernels {
[all …]
H A Dops.mlir59 gpu.module @kernels {
119 …// CHECK: gpu.launch_func @kernels::@kernel_1 blocks in (%{{.*}}, %{{.*}}, %{{.*}}) threads in (%{…
120 …gpu.launch_func @kernels::@kernel_1 blocks in (%cst, %cst, %cst) threads in (%cst, %cst, %cst) arg…
122 …gpu.launch_func @kernels::@kernel_1 blocks in (%cst, %cst, %cst) threads in (%cst, %cst, %cst) dyn…
124 …// CHECK: gpu.launch_func @kernels::@kernel_2 blocks in (%{{.*}}, %{{.*}}, %{{.*}}) threads in (%{…
125 gpu.launch_func @kernels::@kernel_2 blocks in (%cst, %cst, %cst) threads in (%cst, %cst, %cst)
127 …// CHECK: %{{.*}} = gpu.launch_func async [%{{.*}}] @kernels::@kernel_2 blocks in (%{{.*}}, %{{.*}…
128 …%t1 = gpu.launch_func async [%t0] @kernels::@kernel_2 blocks in (%cst, %cst, %cst) threads in (%c…
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/altera/
H A Dsingle-work-item-barrier.rst10 These kernels may be viable single work-item kernels, but will be forced to
11 execute as NDRange kernels if using a newer version of the Altera Offline
15 functions will be treated as single work-item kernels, which could be
/llvm-project-15.0.7/llvm/test/tools/llvm-readobj/ELF/
H A Dnote-amd-invalid-v3.test20 # LLVM-NEXT: amdhsa.kernels:
35 # GNU-NEXT: amdhsa.kernels:
50 ## Desc contains 'amdhsa.kernels' without valid entries.
H A Dnote-amd-valid-v3.s19 #LLVM-NEXT: amdhsa.kernels:
45 # GNU-NEXT: amdhsa.kernels:
66 amdhsa.kernels:
H A Dnote-amdgpu.test10 # GNU-NEXT: amdhsa.kernels:
44 # LLVM-NEXT: amdhsa.kernels:
86 # amdhsa.kernels:
H A Dnote-amdgpu-invalid.s11 # GNU-NEXT: amdhsa.kernels:
42 # LLVM-NEXT: amdhsa.kernels:
/llvm-project-15.0.7/mlir/test/Integration/GPU/ROCM/
H A Dprintf.mlir13 gpu.module @kernels {
24 gpu.launch_func @kernels::@hello
/llvm-project-15.0.7/llvm/test/Transforms/OpenMP/
H A Dgpu_kernel_detection_remarks.ll1 ; RUN: opt -passes=openmp-opt-cgscc -pass-remarks-analysis=openmp-opt -openmp-print-gpu-kernels -di…
2 ; RUN: opt -openmp-opt-cgscc -pass-remarks-analysis=openmp-opt -openmp-print-gpu-kernels -di…
/llvm-project-15.0.7/mlir/test/Conversion/GPUToVulkan/
H A Dlower-gpu-launch-vulkan-launch.mlir21 gpu.module @kernels {
29 gpu.launch_func @kernels::@kernel
/llvm-project-15.0.7/polly/docs/
H A DArchitecture.rst6 extracts interesting loop kernels. For each kernel a mathematical model is
8 accesses in the kernels. Within Polly a variety of analysis and code
64 likely better and it is less likely that kernels that in C seem a perfect fit
82 kernels is generally very fast and the actual optimization and cleanup passes
83 are only run on functions which contain loop kernels that are worth optimizing.
/llvm-project-15.0.7/llvm/test/MC/AMDGPU/
H A Dhsa-metadata-kernel-args-v3.s6 ; CHECK: amdhsa.kernels:
59 amdhsa.kernels:
H A Dhsa-metadata-kernel-code-props-v3.s30 amdhsa.kernels:
H A Dhsa-metadata-kernel-attrs-v3.s45 amdhsa.kernels:
/llvm-project-15.0.7/mlir/test/mlir-vulkan-runner/
H A Daddf.mlir9 gpu.module @kernels {
40 gpu.launch_func @kernels::@kernel_add
H A Dmulf.mlir9 gpu.module @kernels {
41 gpu.launch_func @kernels::@kernel_mul
H A Dtime.mlir12 gpu.module @kernels {
47 gpu.launch_func @kernels::@kernel_add
H A Dsubf.mlir10 gpu.module @kernels {
44 gpu.launch_func @kernels::@kernel_sub
H A Daddi.mlir9 gpu.module @kernels {
39 gpu.launch_func @kernels::@kernel_addi
H A Daddi8.mlir9 gpu.module @kernels {
40 gpu.launch_func @kernels::@kernel_addi
/llvm-project-15.0.7/mlir/test/mlir-spirv-cpu-runner/
H A Ddouble.mlir12 gpu.module @kernels {
58 gpu.launch_func @kernels::@double

123456