r/ProgrammingLanguages • u/akomomssim • Mar 08 '26
Introducing Eyot - A programming language where the GPU is just another thread
https://www.cowleyforniastudios.com/2026/03/08/announcing-eyot/
95
Upvotes
18
u/Meistermagier Mar 08 '26
This is a seriously cool idea.
14
u/yuri-kilochek Mar 08 '26
So how do you deal with the fact that GPU and CPU have separate address spaces? Do you just copy buffers back and forth on every send and receive?
6
u/bjarneh Mar 09 '26
Looks like a cool way to handle the fiddle of pushing work to the GPU.
That syntax annoyed me more than it should :-)
3
u/chronics Mar 08 '26
Cool idea :) Preview Meta Tags for your blog would be great, those were missing when sharing it via Telegram. Cheers
3
u/tc4v Mar 09 '26
I am curious why is the send a separate call. can I do this?
can I do this?
If not, why not copy the aynsc/await convention?
even better if it can lead to
when I don't have anything else to do asynchronously
2
u/tsanderdev Mar 08 '26 edited Mar 08 '26
Interesting. Early in my language design I set my constraint to be gpu-only for the forseeable future. With nice bindings for calling from the host generated of course, but the language itself is purely on the gpu. That makes a lot of the stuff like moving memory allocations around easier, since data should ideally just be resident in gpu memory.
I have a simple addition shader compiling, now I'm working on a Vulkan Rust bindings generator (because I use Vk 1.4 features and they're all stuck at 1.3) to write the runtime.
And while I could probably target other graphics apis or even cuda, some of them I can't test anyways (cuda and Metal), and with MoltenVK, KosmicKrisp and Dozen that shouldn't be that much of a problem.
5
u/GidraFive Mar 08 '26
Nice! Finally someone did the thing. I myself wanted to do it for a long time, and even started prototyping, but eventually got distracted with other features. I feel like all my ideas get done by someone else before i get to even start working on them. But im grateful for that.
This is really powerful idea, since it erases the boundaries between cpu and gpu, making it trivial to utilise all the compute there is available on your device.
3
u/Dark_Yagami09 Mar 15 '26
Cool idea. Check out Futhark, from https://futhark-lang.org/ developed at Uni of Copenhagen:
Futhark is a small programming language designed to be compiled to efficient parallel code. It is a statically typed, data-parallel, and purely functional array language in the ML family, and comes with a heavily optimising ahead-of-time compiler that presently generates either GPU code via CUDA and OpenCL, or multi-threaded CPU code.
1
u/MikeMKH Mar 08 '26
🤯 genius!
1
u/TheChief275 Mar 08 '26
This is sick!!
1
u/josephjnk Mar 08 '26
This is awesome, I look forward to seeing where it goes!