codeplay/oneapi nvidia plugin?

[CFR]

Is codeplay still supporting the nvidia plugin for OneAPI?  Their webpage to select a version only goes up to 2025.1.  When you pick the pulldown option for like 2025.1/all/Linux it just throws you back to the page to pick the pulldown options again (i.e. endless loop).  The options to contact codeplay support (bug message, discord) also seem busted.

Trying to go to the download page directly (https://developer.codeplay.com/api/v1/products/download) results in 404.

OneApi 2025.3 has been out for almost 2 months and we have CUDA 12/13 to deal with.

Just wondering where things stand and are going forward....

[luoliawow]

Same question. I have tried all the provided method, the `spack/wget method` would redierct to 404 page as metioned as @CFR . The `apt` public key of codeplay also returned a 404 page. Trying to specify platform and version is just looping in the download page

[airmenraid · Accepted solution]

FYI, the Intel oneAPI toolkit 2025.3.0 release notes say

CUDA/HIP adapters: Starting in 2025.3 release, CUDA and HIP adapters are no longer available in binary packages. Instead, they will be provided in source format together with the SYCL open-source compiler.

I had an issue getting the Unified Runtime to work with Intel oneAPI 2025.3 (see here for a bug I reported) but a combination that worked for me was Intel oneAPI 2025.2 + Unified Runtime v6.2.1.

[ChristopherW]

Regarding the above-mentioned bug and that the 2026.1 release notes (Intel® oneAPI DPC++/C++ Compiler Release Notes) still suggest to build the 3.6.0 release, which seems not to work even with 2025.3, and causes me a SEGfault with the 2026.1 sycl-ls (on Ubuntu 22.04):

Is there any working documentation how to get this running with oneAPI 2026.1 ? Is it possible at all?

- as there seem to be no releases after 3.6.0, which commit in the dpcpp repo should I check out?

- what is the correct way to build it? cmake seems to have been replaced by some python scripts. Does it matter what Compiler I build it with? Or is there even a binary release I can use?

- what I have to do to make the adapters visible in the OneAPI world? The latest sycl-ls does not seem to use UR_ADAPTERS_SEARCH_PATH any more.

I've been spending two days now trying to try to get things working together, and am pretty frustrated by now.  Is anyone using this successfully?

[CFR]

Thanks for the information.

I can foresee lots of compatibility confusion in the future.  For example the notes for releases 6.2.0 and 6.2.1 both seem to talk mostly about 2025.2.  (Witness your problems as well).

Still, it's good to know how it's supposed to work.

[CFR]

I wish I could provide some insight, but I couldn't get the plugin version and builds sorted out so we just gave up on OneAPI/SYCL.