4 ms·
> Apparently when you run-time compile a CUDA kernel with NVRTC, the default search path does not include the CUDA include directory, so this header cannot be f
by Aardwolf 4y ago
> Apparently when you run-time compile a CUDA kernel with NVRTC, the default search path does not include the CUDA include directory, so this header cannot be found.
I don't know much about futhark nor cuda includes, but if futhark supports cuda, wasn't this already an issue before adding f16 support, to find the headers of other main functionality of cuda? Or is f16 the first thing in cuda that needs a header and other things like regular float computations work without any includes at all?
- Athas 4y agoYou always had to tell Futhark about the CUDA include directory at compile-time. The difference is that now you also have to tell it about it at run-time. Further, at compile-time the usual CPATH/LIBRARY_PATH environment variables are respected, which I think is not the case for the run-time NVRTC compiler.