-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does jitify supports CUDA 11.x??? #91
Comments
We actively use it as part of FLAMEGPU2 (https://github.com/FLAMEGPU/FLAMEGPU2). We've been using it with CUDA versions from 10.2-11.4, without any problems related to changes within CUDA. |
@Robadob |
I'm not sure what example you're referring to, but operator overloading works. We've used operator overloads in some of our own code (e.g.) and it's also heavily use by GLM a header library we sometime use within NVRTC compiled kernels. The main challenge with NVRTC compilation is that host code and system headers are not supported. So you have to be very careful in what the compiler sees. Jitify only helps in this manner by providing an incomplete set of drop-in system header replacements that might be wanted in device code. There can still be some effort required to get existing headers to be supported by NVRTC/Jitify. |
@Robadob thanks for ur reply. i tried to overload operator in the a header which will be included in my kernel source. And it works, that's nice. i will keep following this header and your job ,it's really helpful. thank you again. |
i really appreciate for y'all to provide this nice header. it's really helpful. but it seems to stop updating for a long time ? so does it support latest CUDA version?? thanks!
The text was updated successfully, but these errors were encountered: