mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

339K
active users

#sycl

3 posts3 participants1 post today

My brain is absolutely fried.
Today is the last day of coursework submissions for this semester. What a hectic month.
DNN with PyTorch, Brain model parallelisation with MPI, SYCL and OpenMP offloading of percolation models,hand optimizing serial codes for performance.
Two submissions due today. Submitted one and finalising my report for the second one.
Definitely having a pint after this

#sycl#hpc#msc

Started SYCL this semester in my MSc, and I have a coursework on it.
I have never been more frustrated in my life.
I am not saying SYCL is bad. I might just be too dumb to master it in a sem in order to port an existing CPU code to use MPI & SYCL together.
CUDA was much easier for me for the same task.

Continued thread

Even now, Thrust as a dependency is one of the main reason why we have a #CUDA backend, a #HIP / #ROCm backend and a pure #CPU backend in #GPUSPH, but not a #SYCL or #OneAPI backend (which would allow us to extend hardware support to #Intel GPUs). <doi.org/10.1002/cpe.8313>

This is also one of the reason why we implemented our own #BLAS routines when we introduced the semi-implicit integrator. A side-effect of this choice is that it allowed us to develop the improved #BiCGSTAB that I've had the opportunity to mention before <doi.org/10.1016/j.jcp.2022.111>. Sometimes I do wonder if it would be appropriate to “excorporate” it into its own library for general use, since it's something that would benefit others. OTOH, this one was developed specifically for GPUSPH and it's tightly integrated with the rest of it (including its support for multi-GPU), and refactoring to turn it into a library like cuBLAS is

a. too much effort
b. probably not worth it.

Again, following @eniko's original thread, it's really not that hard to roll your own, and probably less time consuming than trying to wrangle your way through an API that may or may not fit your needs.

6/

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

HiPEAC 2025 kicks off next week and we're excited to be featured in two great sessions on Safety Critical and developing highly parallel applications. If you're attending HiPEAC in Barcelona, be sure to come and see us!

More information in this sessions: khronos.org/events/hipeac-2025
#SYCL #opencl #vulkan

The Khronos Group · HiPEAC 2025Deploying and developing royalty-free open standards for 3D graphics, Virtual and Augmented Reality, Parallel Computing, Neural Networks, and Vision Processing

We're used to leaning on children's books in Computer Science - with Gulliver's big-endian vs little-endian. Back at Supercomputing hashtag#SC24, I spoke at the hashtag#Intel booth all about open standards, performance portability, and the journey up the Yellow Brick Road to see the Wizard of Oz. Check out the video of the talk on YouTube:
youtu.be/xO8FGAOScpo?si=_BnVil
#performanceportability #OpenMP #SYCL