gov ● Advanced Leadership Computing Facility (ALCF) ○ Computer Scientist ○ Kokkos (SYCL/DPC++ backend) ○ Vice Chair WG21 Library Evolution Working Group Incubator (LEWGI / SG18) ○ SYCL Committee com 6Agenda 1. SYCL, oneAPI, and ecosystem 2. SYCL 2020 features • Moving with the Times and Any Backend • Memory Spaces and Dimensions • Reductions and Group Algorithms 3. SYCL futures 9© The Khronos® porting of standard C++ applications to SYCL Closer alignment and integration with ISO C++ Multiple Backend acceleration and API independent SYCL 2020 increases expressiveness and simplicity for modern

SOLUTIONS 110 When the unit wakes up, send the last 100 lines from the application log to the backend using the event service.PROBLEMS & SOLUTIONS 111 ❑ tail -n 100 /var/log/my_log.txt shortLog ❑ send the last 100 lines from the application log to the backend using the event service.Good example to good enough solution 112 80% result / 20% effortPROBLEMS 113 ⊡ Unexplained resets. ⊡ Not enough & SOLUTIONS 125 RF receiver UART (Serial port) BACKEND READy concentratorPROBLEMS & SOLUTIONS 126 RF receiver UART (Serial port) BACKEND READy concentrator Once in a while we stopped receiving

programming SYCL 2020 C++17 Single source programming Many backend options SYCL 202X C++20 Single source programming Many backend options C++11 C++14 C++17 C++20 OpenCL 3.0 C++23SYCL IMPLEMENTATIONS ▪ Precursor to span & mdspan ▪ “Any failure to meet array_view’s bounds-safety constraints will result in a call to std::terminate() (a “fail-fast” approach to safety). This is a critical aspect of ▪ Precursor to span & mdspan ▪ “Any failure to meet array_view’s bounds-safety constraints will result in a call to std::terminate() (a “fail-fast” approach to safety). This is a critical aspect of

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. It is recommended be used, but it is under active development and the interfaces, APIs or behavior might change as a result of evolution, and this will not be considered breaking. If you are interested in these features you CLI also sends all the information, warning, and error messages to stderr, while keeping the final result in stdout, allowing multiple output formats like --format=html or --format=json and using redirects

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. It is recommended be used, but it is under active development and the interfaces, APIs or behavior might change as a result of evolution, and this will not be considered breaking. If you are interested in these features you CLI also sends all the information, warning, and error messages to stderr, while keeping the final result in stdout, allowing multiple output formats like --format=html or --format=json and using redirects

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. It is recommended be used, but it is under active development and the interfaces, APIs or behavior might change as a result of evolution, and this will not be considered breaking. If you are interested in these features you CLI also sends all the information, warning, and error messages to stderr, while keeping the final result in stdout, allowing multiple output formats like --format=html or --format=json and using redirects

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. It is recommended be used, but it is under active development and the interfaces, APIs or behavior might change as a result of evolution, and this will not be considered breaking. If you are interested in these features you CLI also sends all the information, warning, and error messages to stderr, while keeping the final result in stdout, allowing multiple output formats like --format=html or --format=json and using redirects

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. It is recommended be used, but it is under active development and the interfaces, APIs or behavior might change as a result of evolution, and this will not be considered breaking. If you are interested in these features you CLI also sends all the information, warning, and error messages to stderr, while keeping the final result in stdout, allowing multiple output formats like --format=html or --format=json and using redirects

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. It is recommended be used, but it is under active development and the interfaces, APIs or behavior might change as a result of evolution, and this will not be considered breaking. If you are interested in these features you CLI also sends all the information, warning, and error messages to stderr, while keeping the final result in stdout, allowing multiple output formats like --format=html or --format=json and using redirects

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