bashbaug, 2 months ago to random

I couldn't make it to Chicago and IWOCL this year, so I did my best to bring Chicago to me. #IWOCL #OpenCL #SYCL

Brett_E_Carlock, 7 months ago to random

Do I have anyone in my wider network with skills in programming CUDA, SYCL, and OpenCL?

We want to determine feasibility of migrating CUDA-only code to SYCL (via SYCLomatic?): OpenCV feature detection/extraction modules (SIFT, HAGOG, ORB, AKAZE).

The intent is to upstream all feasible work.

This, hopefully, should stand to benefit everyone instead of being limited to NVIDIA.

Currently in info gathering/people connecting phase, not yet funded & ready to go.

#CUDA #SYCL #OpenCL #OpenCV

sri, 8 months ago to random

I'm thinking of engaging with the DCP++ compiler group and getting them change the binary name. (this is the open source clang version) It's clang++/clang++-18 - clashing with other installs.
Could be good to get some community support for the ask. Any thoughts here? #sycl #oneapi

sri, 9 months ago to random

What an amazing talk by @airlied on the state of vendors, compute and community feedback. Please take the 45 minutes to watch - worth every minute! https://youtu.be/HzzLY5TdnZo

#oneapi #sycl #compute #cuda

sri, 11 months ago to rust

For those who have waited eagerly for the recording of our #oneapi meetup with @karolherbst - here it is! https://youtu.be/KUze0JbPSy8
#sycl #opencl #rustlang - if you are interested in joining our oneAPI meetup - feel free to subscribe here - https://www.meetup.com/oneapi-community-us/

Next time we will be meeting with Stephano Cetola who will be talking about RISC-V, onAPI, and other things.

Announcing awesome oneAPI

I recently published a repo based on the popular 'awesome' concept - basically a simple, curated list that talks about impactful projects that are using oneAPI. Check it out at:...

karolherbst, 11 months ago to random

Did a #SyCL CTS run via DPCPP on #Rusticl on my sycl branch: https://gitlab.freedesktop.org/karolherbst/mesa/-/commits/rusticl/sycl/

57% tests passed, 36 tests failed out of 84

not bad, not great, though some fails are not directly rusticls fault:

• bugs inside DPCPP
• invalid SPIR-V generated by DPCPP, had to disable SPIR-V validation
• some tests assume optional CL extensions (like Intel_usm)
• some tests require Program Scope Global Variables, which are pain to implement.

9 of the fails are trivial Mesa, so I'll handle those.

giuseppebilotta, 1 year ago to random

Corporate #FLOSS at its worst: #NVIDIA controls the #Thrust library and its #CUDA, #OpenMP and #TBB backend. #AMD provides rocThrust, that is just Thrust with the CUDA part stripped and a new backend for #ROCm / #HIP. Nobody* is working on a backend for #SYCL
#Intel provides its own #oneAPI alternative as #oneDPL, which is NOT a drop-in replacement.

This is why we can't have nice things.

*there's a dead project here
https://github.com/wdmapp/syclthrust

fclc, 1 year ago to hpc

Time for an #introduction!
I'm a young Canuck with interests/experience in #HPC, #Linux, #BLAS, #SYCL, #C, #AVX512, #Rust, heterogeneous compute & other such things.

Currently my personal projects are bringing #FP16 to the #OpenBLAS library, working to standardize what Complex domain BLAS FP16 kernels/implementations should look like, and making sure #SYCL is available everywhere.

I also write every now and again. Here's the tail of AVX512 FP16 on Alderlake
https://gist.github.com/FCLC/56e4b3f4a4d98cfd274d1430fabb9458