19.0.0__LIBSYCL_MAJOR_VERSION, __LIBSYCL_MINOR_VERSION and __LIBSYCL_PATCH_VERSION)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.
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 expectationsIn 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 testsThe following hardware and software configurations were tested:
Driver versions listed as reported by sycl::device::get_info<info::device::driver_version>().
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 queriestest_header CTS target cannot be compiled, because definition ofSYCL_LANGUAGE_VERSION does not match the latest version of the SYCL 2020test_language CTS target cannot be compiled, because the compiler does notmulti_ptr CTS target cannot be compiled, because implementation fordecorated_generic_ptr and raw_generic_ptr aliases is missing.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
For a more detailed changelog refer to Release notes Jul'24 in our release notes document.
Known issuesThis 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:
clang-cl.exe driver-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.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4