futhark VS langs

There is no on-going work to support Metal apart from the work done by Miles. There's an old issue about it: https://github.com/diku-dk/futhark/issues/853#issuecomment-5...

We actually have a long-standing issue regarding WebGPU[0]. Long story short, we want to support it, and Athas did some exploratory work a couple of years ago and decided that WebGPU wasn't mature enough yet. We already have a WebAssembly backend, so as soon as it is possible to access WebGPU from WebAssembly it should be relatively straightforward.

[0]: https://github.com/diku-dk/futhark/issues/1403

Functional programming can be a great way to handle parallel programming in a sane way. See the Futhark language [1], for example, that accepts high-level constructs like map and convert them to the appropriate machine code, either on the CPU or the GPU.

[1] https://futhark-lang.org/

Futhark - use a functional language to program the gpu

You might want to look into Futhark, although it's mainly designed for writing GPU code.

I recently became aware of a high-level language called Futhark [1] that fits well in that space. It is statically-typed and functional.

Maybe some other array languages work in the GPU as well, I don't know.

[1] https://futhark-lang.org/

Futhark https://futhark-lang.org/

Well, I only wrote a few dozen lines in each. (Those benchmarks I wrote are here, all in one file; scroll through to find them. Those two will be at the end.

Next I tried writing a custom C program just for the VM execute function; mostly this was a framework machine-generated from my interpreter, with the handlers necessary filled in manually.

This is my doswitch/u-based test program, a mini-interpreter executing a loop.

Actually the next thing I did after trying svm.c was to port it to my systems language to see how my compiler managed with it. (Source is here.)

I have taken something away from Forth which is the (a--b) notation that describes the stack behaviour. I use it in these early docs of my IL here.