File: local_addrspace_init.cl

package info (click to toggle)
llvm-toolchain-9 1%3A9.0.1-16.1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 882,388 kB
  • sloc: cpp: 4,167,636; ansic: 714,256; asm: 457,610; python: 155,927; objc: 65,094; sh: 42,856; lisp: 26,908; perl: 7,786; pascal: 7,722; makefile: 6,881; ml: 5,581; awk: 3,648; cs: 2,027; xml: 888; javascript: 381; ruby: 156
file content (20 lines) | stat: -rw-r--r-- 766 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
// RUN: %clang_cc1 %s -triple spir -cl-std=clc++ -emit-llvm -O0 -o - | FileCheck %s

// Test that we don't initialize local address space objects.
//CHECK: @_ZZ4testE1i = internal addrspace(3) global i32 undef
//CHECK: @_ZZ4testE2ii = internal addrspace(3) global %class.C undef
class C {
  int i;
};

kernel void test() {
  __local int i;
  __local C ii;
  // FIXME: In OpenCL C we don't accept initializers for local
  // address space variables. User defined initialization could
  // make sense, but would it mean that all work items need to
  // execute it? Potentially disallowing any initialization would
  // make things easier and assingments can be used to set specific
  // values. This rules should make it consistent with OpenCL C.
  //__local C c();
}