Some good news!

After a little back and forth with intel, managed to get #PETSc built properly with the Intel #LLVM compilers AND #MPI

in the specific case of PETSc, you want to use `./configure --with-debugging=0 --with-cc='mpiicc -cc=icx' --with-cxx='mpiicpc -cxx=icpx' --with-fc='mpiifort -fc=ifx'`

NB however that this doesn't work well (at all?) with nested cmake, which is relied on by PETSc when using --download-kokkos=1 to mirror your build flags when building kokkos from source

The feature I miss the most from Twitter on Mastodon is quote tweets, explicitly of my own for the use case of related but divergent technical threads.

Working on the #GPGPU && #AVX512 accelerated build of #PETSc to enable faster execution of #OpenFOAM as of now and all the relevant threads would have to be independent threads and hard to cross reference as new threads/tangents pop up.

I'll be speaking during the OneAPI dev summit tomorrow, specifically the panel discussion on accelerated computing.

Partially as a meme/Sanity check the challenge of this afternoon:

Can I got from no installs to a GPU accelerated simulation of OpenFOAM using an Arc a770 on Linux?

Plan is #OpenFoam 2212, #petsc 3.19, #OneAPI 2023.1 and #mesa 23 (in case I need to fall back to #OpenCL)