Hi, I work in a large CUDA codebase and use Clang to build some of our CUDA code to improve compilation speed. We're planning to upgrade to CUDA 11 soon, and it appears that CUDA 11 is not yet supported in LLVM.>From the LLVM commits history, I can see that work on CUDA 11 has started. Is this currently being worked on? What is the remaining work left? And is any help needed to finish it?Cheers, Igor -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200730/0fd39711/attachment.html>
On Thu, Jul 30, 2020 at 2:34 PM Igor Sugak <sugak at fb.com> wrote:> I work in a large CUDA codebase and use Clang to build some of our CUDA > code to improve compilation speed. We're planning to upgrade to CUDA 11 > soon, and it appears that CUDA 11 is not yet supported in LLVM. > > From the LLVM commits history, I can see that work on CUDA 11 has started. > Is this currently being worked on? What is the remaining work left? And is > any help needed to finish it? >Clang works with CUDA-11 with feature parity with CUDA-10.1. I.e. whatever code clang was able to compile w/ CUD-10.1 it should still be able to compile w/ 11.0. It supports targeting new GPUs supported by newer CUDA versions, but currently lacks support for the new instruction variants and corresponging LLVM intrinsics and clang builtins (hence the warning, which can be disabled). In the past addition of new features was driven by the practical need for them and there's been little demand for the new bells and whistles. Most of the TensorCore cycles are spent in NVIDIA's own cuBLAS/cuDNN precompiled libraries these days with little to no compileable source code that needs to support TensorCores. Do you have the list of specific CUDA features that you need clang to support? -- --Artem Belevich -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200730/a1af4ffa/attachment.html>
Thanks for the update. I noticed the warning and assumed that it's not yet supported. I'll give it a try and report if there are problems. Igor ________________________________ From: Artem Belevich <tra at google.com> Sent: Thursday, July 30, 2020 3:17 PM To: Igor Sugak <sugak at fb.com> Cc: Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: Status of CUDA 11 support On Thu, Jul 30, 2020 at 2:34 PM Igor Sugak <sugak at fb.com<mailto:sugak at fb.com>> wrote: I work in a large CUDA codebase and use Clang to build some of our CUDA code to improve compilation speed. We're planning to upgrade to CUDA 11 soon, and it appears that CUDA 11 is not yet supported in LLVM.>From the LLVM commits history, I can see that work on CUDA 11 has started. Is this currently being worked on? What is the remaining work left? And is any help needed to finish it?Clang works with CUDA-11 with feature parity with CUDA-10.1. I.e. whatever code clang was able to compile w/ CUD-10.1 it should still be able to compile w/ 11.0. It supports targeting new GPUs supported by newer CUDA versions, but currently lacks support for the new instruction variants and corresponging LLVM intrinsics and clang builtins (hence the warning, which can be disabled). In the past addition of new features was driven by the practical need for them and there's been little demand for the new bells and whistles. Most of the TensorCore cycles are spent in NVIDIA's own cuBLAS/cuDNN precompiled libraries these days with little to no compileable source code that needs to support TensorCores. Do you have the list of specific CUDA features that you need clang to support? -- --Artem Belevich -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200730/9644de7f/attachment.html>