Intel® oneAPI DPC++/C++ Compiler
Talk to fellow users of Intel® oneAPI DPC++/C++ Compiler and companion tools like Intel® oneAPI DPC++ Library, Intel® DPC++ Compatibility Tool, and Intel® Distribution for GDB*

codeplay/oneapi nvidia plugin?

CFR
New Contributor II
512 Views

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....

1 Solution
airmenraid
Beginner
64 Views

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.

View solution in original post

0 Kudos
3 Replies
luoliawow
Beginner
472 Views

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

0 Kudos
airmenraid
Beginner
65 Views

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.

0 Kudos
CFR
New Contributor II
45 Views

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.

0 Kudos
Reply