-
Notifications
You must be signed in to change notification settings - Fork 915
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
Tell jitify_preprocess where to search for libnvrtc #11787
Tell jitify_preprocess where to search for libnvrtc #11787
Conversation
ffeeddc
to
dfe1a24
Compare
Codecov ReportBase: 87.40% // Head: 87.52% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## branch-22.12 #11787 +/- ##
================================================
+ Coverage 87.40% 87.52% +0.11%
================================================
Files 133 133
Lines 21833 21807 -26
================================================
+ Hits 19084 19087 +3
+ Misses 2749 2720 -29
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
rerun tests |
dfe1a24
to
91dfa83
Compare
On machines with multiple CUDA Toolkits installed it is possible to have a mismatch between the version of `nvcc` used to compile code and the version of `libnvrtc` used for the JIT code. This generally occurs when `LD_LIBRARY_PATH` points to a different version of the CUDA Toolkit. We now explicitly specify what toolkit library directory to search when JIT code during libcudf compilation.
91dfa83
to
24932d7
Compare
@gpucibot merge |
Description
On machines with multiple CUDA Toolkits installed it is possible to have a mismatch between the version of
nvcc
used to compile code and the version oflibnvrtc
used for the JIT code. This generally occurs whenLD_LIBRARY_PATH
points to a different version of the CUDA Toolkit.We now explicitly specify what toolkit library directory to search when JIT code during libcudf compilation.
Checklist