#dpcpp — Public Fediverse posts

I'm getting the material ready for my upcoming #GPGPU course that starts on March. Even though I most probably won't get to it,I also checked my trivial #SYCL programs. Apparently the 2025.0 version of the #Intel #OneAPI #DPCPP runtime doesn't like any #OpenCL platform except Intel's own (I have two other platforms that support #SPIRV, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)

I'm getting the material ready for my upcoming #GPGPU course that starts on March. Even though I most probably won't get to it,I also checked my trivial #SYCL programs. Apparently the 2025.0 version of the #Intel #OneAPI #DPCPP runtime doesn't like any #OpenCL platform except Intel's own (I have two other platforms that support #SPIRV, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)

I'm getting the material ready for my upcoming #GPGPU course that starts on March. Even though I most probably won't get to it,I also checked my trivial #SYCL programs. Apparently the 2025.0 version of the #Intel #OneAPI #DPCPP runtime doesn't like any #OpenCL platform except Intel's own (I have two other platforms that support #SPIRV, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)

I'm getting the material ready for my upcoming #GPGPU course that starts on March. Even though I most probably won't get to it,I also checked my trivial #SYCL programs. Apparently the 2025.0 version of the #Intel #OneAPI #DPCPP runtime doesn't like any #OpenCL platform except Intel's own (I have two other platforms that support #SPIRV, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)

I'm getting the material ready for my upcoming #GPGPU course that starts on March. Even though I most probably won't get to it,I also checked my trivial #SYCL programs. Apparently the 2025.0 version of the #Intel #OneAPI #DPCPP runtime doesn't like any #OpenCL platform except Intel's own (I have two other platforms that support #SPIRV, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)

OK but for real: Since the name DPCPP is being deprecated in favor of ICPX with the -fsycl flag, can we please move to the name iSYCL?

Upstream name of the DPCPP project is staying as the reference implementation.

The intel packaged version no longer has a catchy name 😔
#isycl #intel #sycl #DPCPP #HPC

OK but for real: Since the name DPCPP is being deprecated in favor of ICPX with the -fsycl flag, can we please move to the name iSYCL?

Upstream name of the DPCPP project is staying as the reference implementation.

The intel packaged version no longer has a catchy name 😔
#isycl #intel #sycl #DPCPP #HPC

OK but for real: Since the name DPCPP is being deprecated in favor of ICPX with the -fsycl flag, can we please move to the name iSYCL?

Upstream name of the DPCPP project is staying as the reference implementation.

The intel packaged version no longer has a catchy name 😔
#isycl #intel #sycl #DPCPP #HPC

OK but for real: Since the name DPCPP is being deprecated in favor of ICPX with the -fsycl flag, can we please move to the name iSYCL?

Upstream name of the DPCPP project is staying as the reference implementation.

The intel packaged version no longer has a catchy name 😔
#isycl #intel #sycl #DPCPP #HPC

OK but for real: Since the name DPCPP is being deprecated in favor of ICPX with the -fsycl flag, can we please move to the name iSYCL?

Upstream name of the DPCPP project is staying as the reference implementation.

The intel packaged version no longer has a catchy name 😔
#isycl #intel #sycl #DPCPP #HPC