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
The recently released cuDNN 1.3.1 bumps the CUDNN_jll dependency to 9.0, which provides libcudnn.so.9. This is not compatible with the ONNXRunTime CUDA extension, which needs libcudnn.so.8 to be loaded before loading libonnxruntime_providers_cuda.so. Things might still work if libcudnn.so.8 happens to be found in system libraries but that's obviously not something we want to depend on.
For future releases (until we can be compatible with CUDNN 9) we can upper bound cuDNN with
cuDNN = "~1.1, ~1.2, =1.3.0"
but I suspect we also had better retroactively cap the dependency for existing versions (0.4 and up) in the General registry. I know how to prepare a registry PR to that effect if it sounds good.
The text was updated successfully, but these errors were encountered:
The recently released cuDNN 1.3.1 bumps the CUDNN_jll dependency to 9.0, which provides
libcudnn.so.9
. This is not compatible with the ONNXRunTime CUDA extension, which needslibcudnn.so.8
to be loaded before loadinglibonnxruntime_providers_cuda.so
. Things might still work iflibcudnn.so.8
happens to be found in system libraries but that's obviously not something we want to depend on.For future releases (until we can be compatible with CUDNN 9) we can upper bound cuDNN with
but I suspect we also had better retroactively cap the dependency for existing versions (0.4 and up) in the General registry. I know how to prepare a registry PR to that effect if it sounds good.
The text was updated successfully, but these errors were encountered: