You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RMM turns off the async allocator depending on what is available in the linked cudart. We have been linking cudart statically, but we haven't set this preprocessor directive (RMM_STATIC_CUDART) that actually lets RMM know that we did, so it tries to dynamically load cudart symbols, which could lead to picking up a libcudart.so that isn't the one we statically linked with (an older one, without ASYNC support).
We found this bug when trying the ASYNC allocator again in 22.06. We need to fix in the cudfjni targets.
The text was updated successfully, but these errors were encountered:
abellina
changed the title
[BUG] RMM_STATIC_CUDART needs to be set when statically linking cudart
[BUG] RMM_STATIC_CUDART needs to be set when statically linking cudart in JNI
Apr 4, 2022
…UDA runtime (#10585)
Fixes#10571.
This fixes the JNI CMakeLists.txt so that RMM will automatically get the `RMM_STATIC_CUDART` define added to the build when `CUDA_STATIC_RUNTIME=ON`. Verified by building with Javva CI Dockerfile with static CUDA runtime and examining the build command-lines and flag definitions in java/target/cmake-build/CMakeFiles.
Authors:
- Jason Lowe (https://github.com/jlowe)
Approvers:
- Alessandro Bellina (https://github.com/abellina)
URL: #10585
RMM turns off the async allocator depending on what is available in the linked cudart. We have been linking cudart statically, but we haven't set this preprocessor directive (
RMM_STATIC_CUDART
) that actually lets RMM know that we did, so it tries to dynamically load cudart symbols, which could lead to picking up a libcudart.so that isn't the one we statically linked with (an older one, without ASYNC support).We found this bug when trying the ASYNC allocator again in 22.06. We need to fix in the
cudfjni
targets.The text was updated successfully, but these errors were encountered: