2 ms·
Hooray! I've been playing with Futhark from time to time (and it's lovely). I have eagerly been awaiting this development! This is great! I write much of my c
by sspiff 9y ago
Hooray! I've been playing with Futhark from time to time (and it's lovely).
I have eagerly been awaiting this development! This is great!
I write much of my code in Rust these days and being able to generate plain C entrypoints to my Futhark functions will allow me to bridge both worlds :)
- Athas 9y agoThat's good to hear! You will probably encounter some limitations due to the missing support for error recovery. When you do, we'd very much like to hear from you, to get an understanding of what a proper solution should look like. For example, we probably should not handle "catastrophic" errors like GPU/compiler bugs the same way we handle "incidental" errors like bounds check failures. The former might well poison the entire context, while the latter should permit subsequent entry points to work.
- sspiff 9y agoI have a question regarding the new library generation: is this also supported by futhark-c (or are there plans to support this down the line)? I'd like to be able to fall back to CPU execution when OpenCL is not available on a platform. I realize this means I will need to reduce the problem set significantly, but it would be nice to be able to run a small demo on unsupported platforms as well.
- Athas 9y agoYes, both futhark-c and futhark-opencl use the exact same infrastructure.