home.social

#oneapi — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #oneapi, aggregated by home.social.

  1. 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 …)

  2. I should mention that this isn't just a matter of the dominant player intentionally boycotting standards that would make them lose the vendor lock-in advantage (hello #NVIDIA). All major vendors are guilty of this one way or the other. For example, #AMD unjustifiably pulled (or maybe failed to add) #SPIR and #CPU support from their new #OpenCL implementation. #Intel's #oneAPI (even while still leveraging the OpenCL backend) effectively failed on any other OpenCL platform.

  3. I should mention that this isn't just a matter of the dominant player intentionally boycotting standards that would make them lose the vendor lock-in advantage (hello #NVIDIA). All major vendors are guilty of this one way or the other. For example, #AMD unjustifiably pulled (or maybe failed to add) #SPIR and #CPU support from their new #OpenCL implementation. #Intel's #oneAPI (even while still leveraging the OpenCL backend) effectively failed on any other OpenCL platform.

  4. I should mention that this isn't just a matter of the dominant player intentionally boycotting standards that would make them lose the vendor lock-in advantage (hello #NVIDIA). All major vendors are guilty of this one way or the other. For example, #AMD unjustifiably pulled (or maybe failed to add) #SPIR and #CPU support from their new #OpenCL implementation. #Intel's #oneAPI (even while still leveraging the OpenCL backend) effectively failed on any other OpenCL platform.

  5. .@Intel Advanced Matrix Extensions [AMX] Performance With Xeon Scalable #SapphireRapids

    -- The big #AI performance uplift and power efficiency benefits from #AMX w/ #oneAPI #oneDNN & #OpenVINO benchmarks

    phoronix.com/review/intel-xeon

    Original tweet : twitter.com/phoronix/status/16