shady VS llvm

Sounds cool, but this requires yet another language to learn[0]. As someone who only has limited knowledge in this space, could someone tell me how comparable is the compute functionality of rust-gpu[1], where I can just write rust?

[0] https://github.com/Hugobros3/shady#language-syntax

[1] https://github.com/EmbarkStudios/rust-gpu

Intel's modern compilers (icx, icpx) are clang-based. There is an open-source version [1], and the closed-source version is built atop of this with extra closed-source special sauce.

AOCC and ROCm are also based on LLVM/clang.

[1] https://github.com/intel/llvm

You are not missing anything spec-wise, it is just that particular version of the compiler/runtime doesn't support that query. Support for it was added in intel/llvm#7937 and it should be available in the next oneAPI release.

Install the Intel OpenCL CPU Runtime. AMD CPUs are x86-64 too, so they work just like Intel CPUs do. Afaik, performance is significantly better than with POCL. This also works with EPYC, like the new 96-core Genoa.

The Meson build system Version: 1.0.0 Source dir: /var/home/sri/Projects/simple-oneapi Build dir: /var/home/sri/Projects/simple-oneapi/builddir Build type: native build Project name: simple-oneapi Project version: 0.1.0 C compiler for the host machine: clang (clang 16.0.0 "clang version 16.0.0 (https://github.com/intel/llvm 08be083e07b1fd6437267e26adb92f1b647d57dd)") C linker for the host machine: clang ld.bfd 2.34 C++ compiler for the host machine: clang++ (clang 16.0.0 "clang version 16.0.0 (https://github.com/intel/llvm 08be083e07b1fd6437267e26adb92f1b647d57dd)") C++ linker for the host machine: clang++ ld.bfd 2.34 Host machine cpu family: x86_64 Host machine cpu: x86_64 Build targets in project: 1 Found ninja-1.11.1.git.kitware.jobserver-1 at /var/home/sri/.local/bin/ninja

$ sudo mkdir -p /opt/intel $ sudo mkdir -p /etc/OpenCL/vendors/intel_fpgaemu.icd $ cd /tmp $ wget https://github.com/intel/llvm/releases/download/2022-WW50/oclcpuexp-2022.15.12.0.01_rel.tar.gz $ wget https://github.com/intel/llvm/releases/download/2022-WW50/fpgaemu-2022.15.12.0.01_rel.tar.gz $ sudo bash # cd /opt/intel # mkdir oclfpgaemu- # cd oclfpgaemu- # tar xvfpz /tmp/fpgaemu-2022.15.12.0.01_rel.tar.gz # cd .. # mkdir oclcpuexp_ # cd oclcpuexp- # tar xvfpz /tmp/oclcpuexp- # cd ..

oneAPI includes an implementation of SYCL called DPC++. This implementation supports Intel, Nvidia and AMD GPUs (currently for Nvidia and AMD you need to build the support from the source) but oneAPI also includes some libraries too like oneDNN and oneMKL that use SYCL.

Yes, you can use multiple backends with the same compiled binary. For example you can use DPC++ with Nvidia, AMD and Intel GPU at the same time. ComputeCpp also has the ability to output a binary that can target multiple targets. Each backend generates the ISA for each GPU, and then the SYCL runtime chooses the right one at execution time. There is no ODR violation because each GPU executable is stored on separate ELF sections and loaded at runtime : the C++ linker does not see them. The code doesn't need to have any layers, the only changes you might (but don't have to) make are to optimize for specific processor features.

Intel LLVM SYCL oneAPI DPC++ - an open source implementation of SYCL that is being contributed to the LLVM project

I'm using intel cpu, and after reading this i'm just curious can i set this up with portage? Are there any ebuilds to build this? Do i need whole toolchain from intel site (3Gb+) or just 300 mb tar from their github?