Replies: 3 comments
-
Hi @csccva,
Our OpenCL CPU Runtime supports loading through Khronos OpenCL ICD Loader (and that's in fact is the main way of how it should be used). The flow here is that SYCL RT through some so-called plugins or adapters libraries is linked to Note that the runtime itself can be placed in any directory as long as OpenCL ICD Loader can discover it. As you can see in Registering ICDs, default locations where the loader is looking for instructions where to find runtimes require access to Those variables are called debug ones, but in fact they are pretty stable and we have been using them in our own testing environments for quite a while. So, this is probably a not 100% production-quality solution, but it should be stable and reliable enough. There is an alternative, but way more hacky way. If I'm not mistaken,
Hope this helps |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply. I started to do as you instructed, but during the process I found out that I can actually install everything I needed.
|
Beta Was this translation helpful? Give feedback.
-
Hello, Sorry for the delay in answering I thought I replied already here. I managed to do what I wanted by installing the Intel base kit 2024 and then I downloaded from codeplay the nvidia/amd plug ins and apply the patch. This way I was able to get mky sycl codes running on CPUs and also on nvidia or amd GPUs. Cristian |
Beta Was this translation helpful? Give feedback.
-
Hello,
I managed to compile intel llvm on a cluster with nvidia gpus. Everything works for nvidia targets, but I am not able to use cpu targets.
From these instructions I figure that the opencl runtime for cpus is needed, but I can figure out how to integrate it my build as a normal user.
EDIT:
I tried to use as target
native_cpu
, but this option does not find any device. I get this error:Beta Was this translation helpful? Give feedback.
All reactions