Closed dcz-self closed 10 months ago
There is a long tail of places where Futhark will call abort() or exit() or similar - although I think we fixed almost all of the ones that are not in initialisation. Nevertheless, they should all be considered bugs and fixed. I think this one will be quite easy.
When running an OpenCL backend on a system without any OpenCL devices,
futhark_context_new
will exit with a message:This is rather annoying for portable programs: I'd like the program to be able to try different backends until it finds a working one, rather than tasking the operator to do it manually. I might also want to fall back on non-Futhark code if context creation fails.