Skip to content
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

Embed build-time nvjitlink version and make accessible #38

Closed
vyasr opened this issue Jan 11, 2024 · 2 comments · Fixed by #92
Closed

Embed build-time nvjitlink version and make accessible #38

vyasr opened this issue Jan 11, 2024 · 2 comments · Fixed by #92

Comments

@vyasr
Copy link
Contributor

vyasr commented Jan 11, 2024

pynvjitlink should embed the CUDA version used at build-time as a compile-time constant accessible via a Python API. That would be very helpful for us for debugging in the future. Since we're statically linking our only recourse for debugging purposes right now is to check when a particular pynvjitlink package was built and then see what version of CUDA the build scripts used at that time.

Once we provide this constant, we could also automatically check at import-time whether the CUDA runtime/driver on the system could lead to version mismatches that are unsupported by the current version of pynvjitlink.

Originally posted by @vyasr in #33 (comment)

@jakirkham
Copy link
Member

Would also recommend we do a version check during import pynvjitlink and error informatively if we find a mismatch

@gmarkall
Copy link
Contributor

Perhaps we should do this by exposing nvJitLinkVersion() rather than adding our own logic to capture the build-time version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants