Lines Matching refs:OpenCL
17 OpenCL Support
20 Clang has complete support of OpenCL C versions from 1.0 to 3.0.
21 Support for OpenCL 3.0 is in experimental phase (:ref:`OpenCL 3.0 <opencl_300>`).
23 Clang also supports :ref:`the C++ for OpenCL kernel language <cxx_for_opencl_impl>`.
28 Details about usage of clang for OpenCL can be found in :doc:`UsersManual`.
33 - For general issues and bugs with OpenCL in clang refer to `the GitHub issue
45 This section acts as internal documentation for OpenCL features design
50 OpenCL Metadata
53 Clang uses metadata to provide additional OpenCL semantics in IR needed for
54 backends and OpenCL runtime.
59 <https://www.khronos.org/registry/OpenCL/specs/opencl-1.2.pdf#167>`_
63 kernel code to be added e.g. kernel parameter names will appear in the OpenCL
66 The IDs used to encode the OpenCL's logical address spaces in the argument info
71 OpenCL Specific Options
75 following options specific to the OpenCL frontend.
86 default the OpenCL headers are not loaded by the frontend and therefore certain
89 section on the OpenCL Header <opencl_header>`):
112 To enable modules for OpenCL:
118 Another way to circumvent long parsing latency for the OpenCL builtin
146 memory architectures that do not have separate IDs for each of the OpenCL
159 OpenCL builtins
164 There are some standard OpenCL functions that are implemented as Clang builtins:
168 the OpenCL v2.0 kernel language specification.
195 - OpenCL specific code in ``SemaLookup.cpp``. When ``Sema::LookupBuiltin``
197 to a valid OpenCL builtin function. If so, all overloads of the function are
201 OpenCL Extensions and Features
204 Clang implements various extensions to OpenCL kernel languages.
234 Note that by default targets like `SPIR-V`, `SPIR` or `X86` expose all the OpenCL
246 ``OpenCLBuiltins.td`` detailed in :ref:`OpenCL builtins <opencl_builtins>`.
253 :ref:`the section on the OpenCL Header <opencl_header>`. The macros indicating
277 Note that some legacy extensions (published prior to OpenCL 3.0) still
290 Clang source code. This addresses spaces can be used along with the OpenCL
291 address spaces however when such addresses spaces converted to/from OpenCL
292 address spaces the behavior is not governed by OpenCL specification.
294 An OpenCL implementation provides a list of standard address spaces using
311 C++ for OpenCL Implementation Status
315 release of C++ for OpenCL Documentation
316 <https://github.com/KhronosGroup/OpenCL-Docs/releases/tag/cxxforopencl-docrev2021.12>`_.
321 with '[C++4OpenCL]' - click `here
329 - Support of C++ for OpenCL 2021 is currently in experimental phase. Refer to
330 :ref:`OpenCL 3.0 status <opencl_300>` for details of common missing
331 functionality from OpenCL 3.0.
342 OpenCL C 3.0 Usage
345 OpenCL C 3.0 language standard makes most OpenCL C 2.0 features optional. Optional
346 functionality in OpenCL C 3.0 is indicated with the presence of feature-test macros
347 (list of feature-test macros is `here <https://www.khronos.org/registry/OpenCL/specs/3.0-unified/ht…
360 OpenCL C 3.0 Implementation Status
363 The following table provides an overview of features in OpenCL C 3.0 and their
417 C++ libraries for OpenCL
421 <https://libcxx.llvm.org/>`_ in OpenCL kernel code using C++ for OpenCL mode.
463 More OpenCL specific C++ library implementations built on top of libcxx