This is heavily related to https://reviews.llvm.org/D114326 and uses a different approach for locating path to CUDA on Windows.
Diff Detail
Unit Tests
Time | Test | |
---|---|---|
230 ms | x64 debian > Clang.Driver::cuda-windows.cu |
Event Timeline
clang/lib/Driver/ToolChains/Cuda.cpp | ||
---|---|---|
137–141 | Sorry, wrong patch. I'll upload it again. |
clang/lib/Driver/ToolChains/Cuda.cpp | ||
---|---|---|
137 | Do we want to keep this as the fall-back for cases when CUDA_PATH is not set? Otherwise, we're risking to break existing users. |
clang/lib/Driver/ToolChains/Cuda.cpp | ||
---|---|---|
137 | That was going to be my question as well (for which I wanted your input). (Technically speaking this won't break existing users since they were only able to access CUDA versions up to 8.0 until now, and we would just remove support for anything older that CUDA 10.0.) |
Next step would be to commit the patch. If you do not have commit access, I can help you with that.
If that's the case, please let me know the name and email you want the commit to be attributed to.
Yes, please. I don't have commit access yet.
You can attribute it to mojca at macports.org, for example.
We also need a fix for unit tests on the CI in order to find the files, but I cannot help with that as I don't know how that works.
Also, I would like to get to do some further "baby steps" towards better support of CUDA on Windows in particular, but I would need some guidelines.
I requested a special channel that would allow a bit of discussion https://discord.com/channels/636084430946959380/.
What would be the best way to shortly discuss the options?
Will do once we sort out the tests.
We also need a fix for unit tests on the CI in order to find the files, but I cannot help with that as I don't know how that works.
You may need to adjust clang/test/Driver/cuda-windows.cu and possibly the mock CUDA installation under clang/test/Driver/Inputs/CUDA-windows.
Email would work. cfe-dev@ list would work, too. Chat does not work well for me -- my reply latency tends to be higher than that of email and it's not as good for keeping a record of the conversation.
Do we want to keep this as the fall-back for cases when CUDA_PATH is not set?
Otherwise, we're risking to break existing users.