Creative Commons Attribution 4.0 International License SYCL Single Source C++ Parallel Programming GPU FPGA DSP Custom Hardware GPU CPU CPU CPU Standard C++ Application Code C++ Libraries ML Frameworks Fusion can give better performance on complex apps and libs than hand-coding AI/Tensor HW GPU FPGA DSP Custom Hardware GPU CPU CPU CPU AI/Tensor HW Other BackendsSYCL 2020 is here! Open Standard / https://www.phoronix.com/scan.php?page=news_item&px=hipSYCL-New-Lite-Runtime https://software.intel.com/content/www/us/en/develop/articles/interoperability-dpcpp-sycl-opencl.html https://www.renesas

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 ISO C++ to (eventually) support integration and deployment of multiple acceleration technologies Level Zero Intel GPUs NVIDIA GPUs Level Zero Intel GPUs AMD GPUs New, not experimental anymore, and works on Ponte Vecchio deployment of multiple acceleration technologies VEO Intel CPUs NEC VEs neoSYCL SX-AURORA TSUBASA TBB Any CPU Samsung PIMS XILINX Versal ACAP LLVM IR FPGA LLVM IR HLS Experimental DPC++ fork DPC++

Real Time Hard Real Time Simple System Don’t care None Complicated System Operating system FPGA/Chip + CPU with operating systemLet’s review a system and decide if an operating system is

don’t care, nor do we need to! ● if it uses a GPU, we don’t care, nor do we need to! ● if it uses an FPGA or a SoC, we don’t care, nor do we need to!function abstraction std::string SpellCheck(std::string

Intel Confidential Department or Event Name 1 © 2023 Intel Corporation and Jeffrey E. Erickson cppcon 2023 1cppcon 2023 Behavioral Modeling in HW/SW Co-design using C++ coroutines Jeffrey E Erickson Erickson, Ph.D. Sebastian Schönberg, Ph.D.© 2023 Intel Corporation and Jeffrey E. Erickson cppcon2023 3 A guide to this presentation First: A story and a problem Then: Address the problem Finally: Integrate Integrate with productionIntel Confidential Department or Event Name 4 © 2023 Intel Corporation and Jeffrey E. Erickson cppcon 2023 4 A Story and a Problem • You’re an embedded software developer working

Image Processing Programming Models Outlook Summary single-precision multiply-add Linux, GCC 13, Intel Xeon W-2145 (2 AVX-512 FMA ports) 1 void peak(benchmark::State& state) { 2 float x = 0.f; 3 fake_modify(x); Image Processing Programming Models Outlook Summary single-precision multiply-add Linux, GCC 13, Intel Xeon W-2145 (2 AVX-512 FMA ports) 1 void peak(benchmark::State& state) { 2 float x = 0.f; 3 fake_modify(x); Image Processing Programming Models Outlook Summary single-precision multiply-add Linux, GCC 13, Intel Xeon W-2145 (2 AVX-512 FMA ports) 1 void peak(benchmark::State& state) { 2 float x = 0.f; 3 fake_modify(x);

CMake integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 17.7 Working with Intel compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 17.8 How version. There are defaults definitions for the most popular ones: gcc, cl.exe, clang, apple-clang, intel, with different configurations of versions, runtimes, C++ standard library, etc. This model is also for example, the intel compiler uses the Visual Studio compiler in Windows environments and gcc in Linux environments. The intel compiler is declared this way in the settings.yml: intel: version: ["11"

CMake integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 17.7 Working with Intel compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 17.8 How version. There are defaults definitions for the most popular ones: gcc, cl.exe, clang, apple-clang, intel, with different configurations of versions, runtimes, C++ standard library, etc. This model is also for example, the intel compiler uses the Visual Studio compiler in Windows environments and gcc in Linux environments. The intel compiler is declared this way in the settings.yml: intel: version: ["11"

CMake integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 17.7 Working with Intel compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 17.8 How version. There are default definitions for the most popular ones: gcc, cl.exe, clang, apple-clang, intel, with different configurations of versions, runtimes, C++ standard library, etc. This model is also for example, the intel compiler uses the Visual Studio compiler in Windows environments and gcc in Linux environments. The intel compiler is declared this way in the settings.yml: intel: version: ["11"

CMake integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 17.7 Working with Intel compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 17.8 How version. There are default definitions for the most popular ones: gcc, cl.exe, clang, apple-clang, intel, with different configurations of versions, runtimes, C++ standard library, etc. This model is also for example, the intel compiler uses the Visual Studio compiler in Windows environments and gcc in Linux environments. The intel compiler is declared this way in the settings.yml: intel: version: ["11"