Skip to content

Releases: intel/llvm

DPC++ daily 2025-02-24

24 Feb 03:45
7d58fad
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-24

DPC++ daily 2025-02-23

23 Feb 03:44
7d58fad
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-23

DPC++ daily 2025-02-22

22 Feb 03:41
7d58fad
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-22

Intel SYCL Compiler release 6.0.0

20 Feb 10:02
v6.0.0
54cbbec
Compare
Choose a tag to compare

Dependencies included in the release

Components included in the release

  • clang version 19.0.0
  • SYCL runtime version 8.0.0 (as indicated by predefined macro __LIBSYCL_MAJOR_VERSION, __LIBSYCL_MINOR_VERSION and __LIBSYCL_PATCH_VERSION)

Compatibility with previous releases

This is a first formal release in this repo and therefore there are no other releases to be compatible with.

However, the repo has existed for a while and this release is not compatible with builds produced from older commits, because there were ABI-breaking changes made to the codebase just prior taking the sycl-rel-6_0_0 branch.

Compatibility with oneAPI

Intel(R) oneAPI DPC++/C++ Compiler version 2025.0 leverages codebase from sycl-rel-6_0_0 branch and it is the closest oneAPI DPC++/C++ compiler release to this one (in terms of available features and bugfixes).

However, this does not guarantee any feature or bugfix parity between these two releases.

Validation & quality expectations

In general, list of supported hardware and operating systems should match the one provided by Intel(R) oneAPI DPC++/C++ Compiler for version 2025.0, see corresponding system requirements.

However, we did not perform the same exaustive testing of this open-source branch and therefore there could be some unique issues that are not present in Intel (R) oneAPI DPC++/C++ Compiler version 2025.0.

You can find full validation logs for the branch here but a summary of it will also be posted below.

End to end tests

The following hardware and software configurations were tested:

Driver versions listed as reported by sycl::device::get_info<info::device::driver_version>().

  • Windows
    • Driver version: 32.0.101.6129
    • Intel(R) oneAPI Unified Runtime over Level-Zero on
      Intel(R) Iris(R) Xe Graphics 12.0.0
    • Intel(R) OpenCL Graphics on Intel(R) Iris(R) Xe Graphics OpenCL 3.0 NEO
  • Linux (Ubuntu 22.04)
    • Intel(R) OpenCL Graphics on Intel(R) Iris(R) Xe Graphics OpenCL 3.0 NEO
    • Intel(R) oneAPI Unified Runtime over Level-Zero on
      Intel(R) Iris(R) Xe Graphics 12.0.0
    • Intel(R) OpenCL on
      11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80 Ghz OpenCL 3.0
    • AMD HIP BACKEND on AMD Radeon RX 6700 XT gfx1031
    • NVIDIA CUDA BACKEND on NVIDIA A10G 8.6

SYCL CTS

  • Linux (Ubuntu 22.04)
    • Intel(R) OpenCL on
      11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80 Ghz OpenCL 3.0
    • Intel(R) oneAPI Unified Runtime over Level-Zero on
      Intel(R) Iris(R) Xe Graphics 12.0.0

We use the latest available CTS in our validation, but sycl-rel-6.0.0 is an
old branch already and there were some CTS changes made which make them fail.

Known failures are:

  • test_device CTS test fails because some OpenCL-specific device info queries
    do not throw exceptions on non-OpenCL backends. See KhronosGroup/SYCL-Docs#625
  • test_header CTS target cannot be compiled, because definition of
    SYCL_LANGUAGE_VERSION does not match the latest version of the SYCL 2020
    specification. See KhronosGroup/SYCL-Docs#634
  • test_language CTS target cannot be compiled, because the compiler does not
    abide to all new rules for constant-evaluated expression from the latest
    version of the SYCL 2020 specification. See KhronosGroup/SYCL-Docs#388
  • multi_ptr CTS target cannot be compiled, because implementation for
    decorated_generic_ptr and raw_generic_ptr aliases is missing.
    See KhronosGroup/SYCL-Docs#598

How to use

This release does not provide a pre-built binaries of our SYCL compiler and
simply marks a known good commit on a corresponding release branch which can be
used for building the compiler and the runtime for your needs. To do so, follow
Get Started Guide

Detailed changelog

For a more detailed changelog refer to Release notes Jul'24 in our release notes document.

Known issues

This section describes additional issues which were reported that are not listed in the corresponding section of the detailed changelog.

error: SYCL kernel cannot call a variadic function

Compilation error like this will be reported for applications that use sycl::vec::operator[] (either directly, or indirectly through built-ins like sycl::group_broadcast) when compiled on Windows in Debug mode using clang.exe compiler driver.

There are a couple of workarounds available to it:

  • switch to using clang-cl.exe driver
  • pass an extra flag during compilation: -Xsycl-target-frontend "-D_CONTAINER_DEBUG_LEVEL=0 -D_ITERATOR_DEBUG_LEVEL=0"

Note that if your environment and application is not what described above (sycl::vec::operator[] usage on Windows in Debug mode through clang.exe compiler driver), then the error is expected to be legit, i.e. device code contains some illegal construct.

DPC++ daily 2025-02-21

21 Feb 04:13
e4d65e0
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-21

DPC++ daily 2025-02-20

20 Feb 03:54
7b9779e
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-20

DPC++ daily 2025-02-19

19 Feb 04:06
bae7012
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-19

DPC++ daily 2025-02-17

17 Feb 04:01
311fdc4
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-17

DPC++ daily 2025-02-16

16 Feb 04:14
311fdc4
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-16

DPC++ daily 2025-02-15

15 Feb 04:11
311fdc4
Compare
Choose a tag to compare
Pre-release

Daily build 2025-02-15