Skip to content

Download links for nvidia and amd pluggins are not valid #9

Description

@csccva

Hello,

Are the Nvidia and AMD pluggins deprecated? can't download anymore. Neither the old links nor the present instructions work.

Best regards,

Cristian-Vasile Achim

Activity

  1. Yohello1 commented on Oct 20, 2025

    @Yohello1

    Hello, can't find them either.

  2. idev2580 commented on Oct 21, 2025

    @idev2580

    Hello, me neither.

  3. fh-igd-mueller-roemer commented on Nov 12, 2025

    @fh-igd-mueller-roemer
  4. csccva commented on Nov 13, 2025

    @csccva
    Author

    I guess they are deprecated, but there is no official announcement. I wonder if compiling DPCPP with AMD/Nvidia support would work.

  5. TTopoo commented on Dec 6, 2025

    @TTopoo

    Hello, I also encountered the same problem. Do you have any good solutions?

  6. mirenradia commented on Dec 17, 2025

    @mirenradia

    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.

  7. csccva commented on Dec 18, 2025

    @csccva
    Author

    I tried it just now. The instructions are not correct. When I run the first cmake configure I get:

    $ pwd
    /<path-to>/DPCPP/llvm
    $ cmake -S . -B build -DUR_BUILD_TESTS=OFF -DUR_ENABLE_TRACING=ON -DUR_BUILD_ADAPTER_CUDA=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX="/scratch/project_2001659/cristian/DPCPP/intel"
    CMake Error: The source directory "/scratch/project_2001659/cristian/DPCPP/llvm" does not appear to contain CMakeLists.txt.
    Specify --help for usage, or press the help button on the CMake GUI.
    

    If I do cd llvm again I get:

    CMake Warning:
      Manually-specified variables were not used by the project:
    
        UR_BUILD_ADAPTER_CUDA
        UR_BUILD_TESTS
        UR_ENABLE_TRACING
  8. mirenradia commented on Dec 18, 2025

    @mirenradia

    I tried it just now. The instructions are not correct. When I run the first cmake configure I get:

    $ pwd
    /<path-to>/DPCPP/llvm
    $ cmake -S . -B build -DUR_BUILD_TESTS=OFF -DUR_ENABLE_TRACING=ON -DUR_BUILD_ADAPTER_CUDA=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX="/scratch/project_2001659/cristian/DPCPP/intel"
    CMake Error: The source directory "/scratch/project_2001659/cristian/DPCPP/llvm" does not appear to contain CMakeLists.txt.
    Specify --help for usage, or press the help button on the CMake GUI.
    

    If I do cd llvm again I get:

    CMake Warning:
    Manually-specified variables were not used by the project:

    UR_BUILD_ADAPTER_CUDA
    UR_BUILD_TESTS
    UR_ENABLE_TRACING
    

    Yeah the instructions are definitely wrong. I presume you're supposed to use the unified-runtime directory.

  9. csccva commented on Dec 18, 2025

    @csccva
    Author

    Thanks for replying. Unfortunately for me our servers do not have the depndencies, so I will try after the next upgrade.

    I tried it just now. The instructions are not correct. When I run the first cmake configure I get:

    $ pwd
    /<path-to>/DPCPP/llvm
    $ cmake -S . -B build -DUR_BUILD_TESTS=OFF -DUR_ENABLE_TRACING=ON -DUR_BUILD_ADAPTER_CUDA=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX="/scratch/project_2001659/cristian/DPCPP/intel"
    CMake Error: The source directory "/scratch/project_2001659/cristian/DPCPP/llvm" does not appear to contain CMakeLists.txt.
    Specify --help for usage, or press the help button on the CMake GUI.
    

    If I do cd llvm again I get:
    CMake Warning:
    Manually-specified variables were not used by the project:

    UR_BUILD_ADAPTER_CUDA
    UR_BUILD_TESTS
    UR_ENABLE_TRACING
    

    Yeah the instructions are definitely wrong. I presume you're supposed to use the unified-runtime directory.

  10. mirenradia commented on Dec 18, 2025

    @mirenradia

    FWIW, I tried using the prebuilt CUDA adapter library from the v6.2.1 release by setting UR_ADAPTERS_SEARCH_PATH appropriately but ended up getting a segfault with the sycl-ls from the 2025.3.1 Intel DPC++ compiler.

  11. mirenradia commented on Dec 19, 2025

    @mirenradia

    I got it to work with oneAPI 2025.2 + Unified Runtime (UR) v6.2.1. I reported a bug with oneAPI 2025.3 + Unified Runtime v6.3.0-rc1 at intel/llvm#20945. The segfault I previously mentioned was due to the differing Unified Memory Framework (UMF) versions (v0.11 in UR 6.2.1 and v1.0 in oneAPI 2025.3).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions