Brown Principal Product Owner, oneAPI & Automotive Currently leading team developing HIP & CUDA backends for DPC++ Background in C++ programming models for heterogeneous systems Worked on ComputeCpp (SYCL) options C++11 C++14 C++17 C++20 OpenCL 3.0 C++23 14SYCL Implementations in Development Multiple Backends in Development There is development on supporting SYCL on even more low-level frameworks. For information: http://sycl.tech Source Code DPC++ Uses LLVM/Clang Part of oneAPI ComputeCpp Multiple Backends triSYCL Open source test bed hipSYCL CUDA and HIP/ROCm Any CPU Any CPU Intel CPUs Intel

in the Khronos ecosystem w/o revealing IP Focus on ease of portability support, capable of many backends, and demonstrated to support many platformsPARALLEL INDUSTRY INITIATIVES 2011 OpenCL 1.2 OpenCL IMPLEMENTATIONS IN DEVELOPMENT Source Code DPC++ Uses LLVM/Clang Part of oneAPI hipSYCL Multiple Backends Any CPU Intel CPUs Intel GPUs Intel FPGAs AMD GPUs Any CPU SYCL enables Khronos to influence experimental anymore, and works on Ponte Vecchio My name has changed to adaptive cpp.Multiple Backends in Development SYCL on even more low-level frameworks. For more information: http://sycl.tech

and resources) that is entirely self-contained (i.e., no external dependencies like production backends). (https://abseil.io/resources/swe-book/html/ch23.html) Any time bits enter or leave your unit "right" answer Make a falsifiable hypothesis: "Our code has no bugs" Finding a bug is a positive result True Positive : Test fails and there is a bug True Negative : Test passes because there are Negative : Test passes but there are bugs PT NT PF NF Part 1: Testing Accuracy 32Accuracy The result of your test matches reality of code Test completely : give bugs no place to hide Test Correctly

The alternative is AdaptiveCPP, a cross compiler based on Clang, and targeting various parallelism backends, including OpenMP. Completion status At present the implementations described above are completed another attempt. This will allow testing Sycl on two different compilers: Intel with optimized TBB backends, and AdaptiveCPP with a more common backend. Supporting material The benchmark is in an open repository:

ConanCenter, assume the use of the latest version of the Conan client, and using an older version may result in failure of packages and recipes created with a newer version of the client. Conan needs Python "4.9": # Make compiler␣ ˓→versions 4.8 and 4.7 compatible # with version4.9:␣ ˓→i.e., they all result in the same package ID for version in ("4.8", "4.7"): compatible_pkg = self.info.clone() compatible_pkg com/conan-io/examples.git $ cd libraries/poco $ conan install ./md5 --install-folder=md5_build This will result in the following layout: md5_build conaninfo.txt conanbuildinfo.txt conanbuildinfo.cmake md5 CMakeLists

ConanCenter, assume the use of the latest version of the Conan client, and using an older version may result in failure of packages and recipes created with a newer version of the client. Conan needs Python "4.9": # Make compiler␣ ˓→versions 4.8 and 4.7 compatible # with version4.9:␣ ˓→i.e., they all result in the same package ID for version in ("4.8", "4.7"): compatible_pkg = self.info.clone() compatible_pkg com/conan-io/examples.git $ cd libraries/poco $ conan install ./md5 --install-folder=md5_build This will result in the following layout: md5_build conaninfo.txt conanbuildinfo.txt conanbuildinfo.cmake md5 CMakeLists

ConanCenter, assume the use of the latest version of the Conan client, and using an older version may result in failure of packages and recipes created with a newer version of the client. Conan needs Python com/conan-io/examples.git $ cd libraries/poco $ conan install ./md5 --install-folder=md5_build This will result in the following layout: md5_build conaninfo.txt conanbuildinfo.txt conanbuildinfo.cmake md5 CMakeLists pkg/1.0@myuser/mychannel:af044f9619574eceb8e1cca737a64bdad88246ad The required package has the same result again af04...46ad. Now we can try using GCC 4.4 (< 4.5): $ conan install pkg/1.0@myuser/mychannel

ConanCenter, assume the use of the latest version of the Conan client, and using an older version may result in failure of packages and recipes created with a newer version of the client. Conan needs Python com/conan-io/examples.git $ cd libraries/poco $ conan install ./md5 --install-folder=md5_build This will result in the following layout: md5_build conaninfo.txt conanbuildinfo.txt conanbuildinfo.cmake md5 CMakeLists pkg/1.0@myuser/mychannel:af044f9619574eceb8e1cca737a64bdad88246ad The required package has the same result again af04...46ad. Now we can try using GCC 4.4 (< 4.5): $ conan install pkg/1.0@myuser/mychannel

ConanCenter, assume the use of the latest version of the Conan client, and using an older version may result in failure of packages and recipes created with a newer version of the client. Conan needs Python com/conan-io/examples.git $ cd libraries/poco $ conan install ./md5 --install-folder=md5_build This will result in the following layout: md5_build conaninfo.txt conanbuildinfo.txt conanbuildinfo.cmake md5 CMakeLists pkg/1.0@myuser/mychannel:af044f9619574eceb8e1cca737a64bdad88246ad The required package has the same result again af04...46ad. Now we can try using GCC 4.4 (< 4.5): $ conan install pkg/1.0@myuser/mychannel

ConanCenter, assume the use of the latest version of the Conan client, and using an older version may result in failure of packages and recipes created with a newer version of the client. Conan needs Python com/conan-io/examples.git $ cd libraries/poco $ conan install ./md5 --install-folder=md5_build This will result in the following layout: md5_build conaninfo.txt conanbuildinfo.txt conanbuildinfo.cmake md5 CMakeLists pkg/1.0@myuser/mychannel:af044f9619574eceb8e1cca737a64bdad88246ad The required package has the same result again af04...46ad. Now we can try using GCC 4.4 (< 4.5): $ conan install pkg/1.0@myuser/mychannel