[3/3] Regardless, none of these address natively compiling...

All posts Julien's posts Post Back to profile

[3/3]
Regardless, none of these address natively compiling to the CPU.
There's promising things like VCC https://shady-gang.github.io/vcc/ but it seems too early and risky to base a project on it for now.

My use case is a raymarching based game engine, where the content is defined in terms of functions representing an SDF.
I want to be able to use these SDF-defining functions and their associated data in CPU and GPU compute for physics and gameplay, and on GPU graphics for rendering.

Like 27 February at 14:36 | Open on mastodon.gamedev.place

3 comments

Doug Binks

@julienbarnoin

- SYCL has potential, but it's not there yet, especially on Windows.
- ISPC on CPU is excellent, but although a test project showed SPIR-V to ISPC was workable for targetting CPU and GPU with the same code, it's not a supported feature. I also don't know if ISPC has a healthy future.

27 February at 14:47 | Open on mastodon.gamedev.place

Jari Komppa 🇫🇮

@dougbinks @julienbarnoin
Plus rocm if you want amd only, and oneapi if you want intel only.. both claim to be open but well, while controlled by a single company, not really.

27 February at 14:49 | Open on mastodon.online

Julien Barnoin

So far my kludgy solution is a mix of C and GLSL, where I can share some header files across the languages for common data structures, with some severe restrictions and terribly ugly macros. I can't share any code, I have to copy and adapt it, so my SDF has to stay in GLSL-land only.

I can actually run my GLSL code on the CPU thanks to llvmpipe, which is cool. But:
- I can't rely on it being available
- I can't debug it with standard tools
- GLSL is very restrictive for general programming

27 February at 14:48 | Open on mastodon.gamedev.place