SYCL
Original author(s)Khronos Group
Developer(s)Khronos Group
Initial releaseMarch 2014 (2014-03)
Stable release
2020 revision 8 (1.2.1) / 19 October 2023 (2023-10-19)[1]
Operating systemCross-platform
PlatformCross-platform
TypeHigh-level programming language
Websitewww.khronos.org/sycl/ sycl.tech

SYCL is a higher-level programming model to improve programming productivity on various hardware accelerators. It is a single-source embedded domain-specific language (eDSL) based on pure C++17. It is a standard developed by Khronos Group, announced in March 2014.

Origin of the name

SYCL (pronounced ‘sickle’) originally stood for SYstem-wide Compute Language,[2] but since 2020 SYCL developers have stated that SYCL is a name and have made clear that it is no longer an acronym and contains no reference to OpenCL.[3]

Purpose

SYCL is a royalty-free, cross-platform abstraction layer that builds on the underlying concepts, portability and efficiency inspired by OpenCL that enables code for heterogeneous processors to be written in a “single-source” style using completely standard C++. SYCL enables single-source development where C++ template functions can contain both host and device code to construct complex algorithms that use hardware accelerators, and then re-use them throughout their source code on different types of data.

While the SYCL standard started as the higher-level programming model sub-group of the OpenCL working group and was originally developed for use with OpenCL and SPIR, SYCL is a Khronos Group workgroup independent from the OpenCL working group since September 20, 2019 and starting with SYCL 2020, SYCL has been generalized as a more general heterogeneous framework able to target other systems. This is now possible with the concept of a generic backend to target any acceleration API while enabling full interoperability with the target API, like using existing native libraries to reach the maximum performance along with simplifying the programming effort. For example, the Open SYCL implementation targets ROCm and CUDA via AMD's cross-vendor HIP.

Versions

SYCL was introduced at GDC in March 2014 with provisional version 1.2,[4] then the SYCL 1.2 final version was introduced at IWOCL 2015 in May 2015.[5]

The latest version for the previous SYCL 1.2.1 series is SYCL 1.2.1 revision 7 which was published on April 27, 2020 (the first version was published on December 6, 2017[6]).

SYCL 2.2 provisional was introduced at IWOCL 2016 in May 2016[7] targeting C++14 and OpenCL 2.2. But the SYCL committee preferred not to finalize this version and to move towards a more flexible SYCL specification to address the increasing diversity of current hardware accelerators, including artificial intelligence engines, which led to SYCL 2020.

The latest version is SYCL 2020 revision 6 which was published on November 13, 2022, an evolution from first release of revision 2 which was published on February 9, 2021,[8] taking into account the feedback from users and implementors on the SYCL 2020 Provisional Specification revision 1 published on June 30, 2020.[9] C++17 and OpenCL 3.0 support are main targets of this release. Unified shared memory (USM) is one main feature for GPUs with OpenCL and CUDA support.

At IWOCL 2021 a roadmap was presented. DPC++, ComputeCpp, Open SYCL, triSYCL and neoSYCL are the main implementations of SYCL. Next Target in development is support of C++20 in future SYCL 202x.[10]

Implementations

  • DPC++: (data parallel C++) is an open source project of Intel to introduce SYCL for LLVM and oneAPI. C++17 and parts of C++20 with SYCL 2020 are base of this Compiler framework.[11][12]
  • ComputeCpp: SYCL 1.2.1 conformant framework of firm Codeplay with community version.[13][14] Now deprecated in favor of DPC++. [15]
  • AdaptiveCpp (formerly hipSYCL and Open SYCL): incomplete 1.2.1 support without Images or OpenCL interop, partly SYCL 2020, supports ROCm (AMD), CUDA (Nvidia), OpenMP (CPUs) and Level Zero (Intel).[16][17]
  • triSYCL: based on C++20, OpenMP and OpenCL, slow development, incomplete, with a version based on top of DPC++[18]
  • neoSYCL: SYCL 1.2.1 nearly complete, for hpc SX-Aurora Tsubasa, no OpenCL specific features like image support[19][20]
  • SYCL-gtx: C++11 support, for OpenCL 1.2+, far from complete, no actual development[21]
  • Sylkan is an implementation of SYCL to Vulkan devices in an experimental state.[22]
  • Polygeist has a fork compiling SYCL through MLIR[23] which is backed by the Inteon company.[24]

Software

  • Gromacs: SYCL 2020 is Part of Gromacs Version 2021.[25]
  • use in automotive industry for autonomous driving with support of ISO 26262.[26]

Resources

Khronos Maintains a list of SYCL resource.[27] Codeplay Software also provides tutorials on the website sycl.tech along with other information and news on the SYCL ecosystem.

License

The source files for building the specification, such as Makefiles and some scripts, the SYCL headers and the SYCL code samples are under the Apache 2.0 license.[28] Details of the license are at: https://www.apache.org/licenses/LICENSE-2.0.html

Comparison with other APIs

The open standards SYCL and OpenCL are similar to the programming models of the proprietary stack CUDA from Nvidia, and HIP from the open-source stack ROCm, supported by AMD.

In the Khronos Group realm, OpenCL and Vulkan are the low-level non-single source API and SYCL is the high-level single-source C++ embedded domain-specific language (eDSL).

CUDA

By comparison, the single-source C++ embedded domain-specific language version of CUDA, which is actually named "CUDA Runtime API", is somewhat similar to SYCL. But there is actually a less known non single-source version of CUDA which is called "CUDA Driver API", similar to OpenCL, and used for example by the CUDA Runtime API implementation itself.

SYCL extends the C++ AMP features relieving the programmer from explicitly transferring the data between the host and devices by using buffers and accessors, by opposition to CUDA (before the introduction of Unified Memory in CUDA 6). But starting with SYCL 2020, it is also possible to use USM instead of buffers and accessors to use a lower-level programming model similar to Unified Memory in CUDA.

SYCL is higher-level than C++ AMP and CUDA since you do not need to build an explicit dependency graph between all the kernels, and provides you automatic asynchronous scheduling of the kernels with communication and computation overlap. This is all done by using the concept of accessors, without requiring any compiler support.

Unlike C++ AMP and CUDA, SYCL is a pure C++ eDSL without any C++ extension, allowing a basic CPU implementation relying on pure runtime without any specific compiler. This is very useful for debugging an application or for prototyping for a new architecture without having the architecture and compiler available yet.

There are at least 3 known SYCL implementations targeting the CUDA backend.

ROCm HIP

ROCm HIP can be seen as a clone of CUDA targeting Nvidia GPU, AMD GPU and x86 CPU. Thus ROCm HIP is a lower-level API compared to SYCL and most of the comments mentioned in the comparison with CUDA do apply.

ROCm HIP has some similarities to SYCL in the sense that it can target various vendors (AMD and Nvidia) and accelerator types (GPU and CPU). But SYCL can target according to the implementation any type of accelerators and any vendors, potentially at the same time, in a single application with the concept of backend. SYCL is also pure C++ while HIP uses some extensions inherited from CUDA, which prevents using a normal C++ compiler to target any CPU.

There are at least 2 known implementations of SYCL targeting the HIP backend, oneAPI DPC++ and Open SYCL. The Open SYCL implementation, over HIP, adds SYCL programming to CUDA and HIP.

Other programming models

SYCL has many similarities to the Kokkos programming model,[29] including the use of opaque multi-dimensional array objects (SYCL buffers and Kokkos arrays), multi-dimensional ranges for parallel execution, and reductions (added in SYCL 2020). Numerous features in SYCL 2020 were added in response to feedback from the Kokkos community.

See also

References

  1. ↑ "Khronos SYCL Registry - the Khronos Group Inc".
  2. ↑ Keryell, Ronan (17 November 2019). "SYCL: A Single-Source C++ Standard for Heterogeneous Computing" (PDF). Khronos.org. Retrieved 26 September 2023.
  3. ↑ Keryell, Ronan. "Meaning of SYCL". GitHub. Retrieved 5 February 2021.
  4. ↑ Khronos Group (19 March 2014). "Khronos Releases SYCL 1.2 Provisional Specification". Khronos. Retrieved 20 August 2017.
  5. ↑ Khronos Group (11 May 2015). "Khronos Releases SYCL 1.2 Final Specification". Khronos. Retrieved 20 August 2017.
  6. ↑ Khronos Group (6 December 2017). "The Khronos Group Releases Finalized SYCL 1.2.1". Khronos. Retrieved 12 December 2017.
  7. ↑ Khronos Group (18 April 2016). "Khronos Releases OpenCL 2.2 Provisional Specification with OpenCL C++ Kernel Language". Khronos. Retrieved 18 September 2017.
  8. ↑ Khronos Group (9 February 2021). "Khronos Releases SYCL 2020 Specification". Khronos. Retrieved 22 February 2021.
  9. ↑ Khronos Group (30 June 2020). "Khronos Steps Towards Widespread Deployment of SYCL with Release of SYCL 2020 Provisional Specification". Khronos. Retrieved 4 December 2020.
  10. ↑ https://www.iwocl.org/wp-content/uploads/k04-iwocl-syclcon-2021-wong-slides.pdf
  11. ↑ https://www.iwocl.org/wp-content/uploads/k01-iwocl-syclcon-2021-reinders-slides.pdf
  12. ↑ "Compile Cross-Architecture: Intel® oneAPI DPC++/C++ Compiler".
  13. ↑ "Home - ComputeCpp CE - Products - Codeplay Developer".
  14. ↑ "Guides - ComputeCpp CE - Products - Codeplay Developer".
  15. ↑ "The Future of ComputeCpp". www.codeplay.com. Retrieved 2023-12-09.
  16. ↑ "AdaptiveCpp (formerly known as hipSYCL / Open SYCL)". GitHub. 4 July 2023.
  17. ↑ "hipSYCL feature support". GitHub. 4 July 2023.
  18. ↑ "triSYCL". GitHub. 6 January 2022.
  19. ↑ Ke, Yinan; Agung, Mulya; Takizawa, Hiroyuki (2021). "NeoSYCL: A SYCL implementation for SX-Aurora TSUBASA". The International Conference on High Performance Computing in Asia-Pacific Region. pp. 50–57. doi:10.1145/3432261.3432268. ISBN 9781450388429. S2CID 231597238.
  20. ↑ Ke, Yinan; Agung, Mulya; Takizawa, Hiroyuki (2021). "NeoSYCL: A SYCL implementation for SX-Aurora TSUBASA". The International Conference on High Performance Computing in Asia-Pacific Region. pp. 50–57. doi:10.1145/3432261.3432268. ISBN 9781450388429. S2CID 231597238.
  21. ↑ "Sycl-GTX". GitHub. 10 April 2021.
  22. ↑ https://www.iwocl.org/wp-content/uploads/14-iwocl-syclcon-2021-thoman-slides.pdf
  23. ↑ "Polygeist". GitHub. 25 February 2022.
  24. ↑ "Inteon". 25 February 2022.
  25. ↑ https://www.iwocl.org/wp-content/uploads/k03-iwocl-syclcon-2021-trevett-updated.mp4.pdf
  26. ↑ https://www.iwocl.org/wp-content/uploads/20-iwocl-syclcon-2021-rudkin-slides.pdf
  27. ↑ "SYCL Resources". khronos.org. Khronos group. 20 January 2014.
  28. ↑ "SYCL Open Source Specification". GitHub. 10 January 2022.
  29. ↑ Hammond, Jeff R.; Kinsner, Michael; Brodman, James (2019). "A comparative analysis of Kokkos and SYCL as heterogeneous, parallel programming models for C++ applications". Proceedings of the International Workshop on OpenCL. pp. 1–2. doi:10.1145/3318170.3318193. ISBN 9781450362306. S2CID 195777149.{{cite book}}: CS1 maint: date and year (link)
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.