CUDNN v8 support#39577
Conversation
|
Hi Nathan, thank you very much for this PR. I'm going to temporarily mark it as 'ready to pull'. This will simplify testing it on our side and merging it. |
|
@nluehr can you please resolve conflicts ? |
Hi Nathan, you don't need to resolve, it's easier to merge this manually from our side and I'm actively working on that. The CUDA 11 changes have been merged already, and hopefully this one will land until Monday as well. There was some trouble with compiler commands going over the Windows character limit and unrelated breakages. I'm removing the 'ready to pull' tag again so the automated tools don't try to submit it as well. |
PiperOrigin-RevId: 314219496 Change-Id: I3e36453044e5b73274e05d84f8d7f2cdb5b144ae
Handle '64_' prefix in the cuDNN version for Windows. PiperOrigin-RevId: 314385732 Change-Id: I9b36497dbe460e2e7cad3d755cf9ce8d41647ce3
…64_' prefix in the cuDNN version for Windows.PiperOrigin-RevId: 314385732Change-Id: I9b36497dbe460e2e7cad3d755cf9ce8d41647ce3
Handle '64_' prefix in the cuDNN version for Windows. PiperOrigin-RevId: 314385732 Change-Id: I9b36497dbe460e2e7cad3d755cf9ce8d41647ce3
|
What was the reason for not using |
Handle '64_' prefix in the cuDNN version for Windows. PiperOrigin-RevId: 314385732 Change-Id: I9b36497dbe460e2e7cad3d755cf9ce8d41647ce3
Just leaving a comment here so that future visitors can get the answer to the above quesiton. |
|
The reason was just to match the behavior with cudnn v7. |
Handle '64_' prefix in the cuDNN version for Windows. PiperOrigin-RevId: 314385732 Change-Id: I9b36497dbe460e2e7cad3d755cf9ce8d41647ce3
Enables building against the CUDNN v8 library.
Attn: @reedwm
Note this PR can be applied separately from the cuda 11 PR (39576), but both modify find_cuda_config.py. As a result, they will conflcit on find_cuda_config.py.gz.base64 and that file will need to be regenerated via compress_find_cuda_config.py when the second PR is merged.