-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set c++17 standard in CMake for recent torch/cuda versions #109
base: master
Are you sure you want to change the base?
Conversation
This is ready to merge. |
CUDA 11.8 build tends to fail due to some form of disk access error when installing CUDA. Must be a bug in the Jimver thingy. There is a new version, lets try with that... |
I have purged the GA cache. If it fails, try to rerun. |
I am not sure if I do not have rights to do so or just do not know how, but I cannot rerun the CI. I will just make a spurious commit. |
11.8 Still refuses to download it seems. |
|
Do you know if this disk limit is per action or per individual check? |
This reverts commit f70c859.
This is ready for review. I had to deal with a couple of quicks in the compilation process for pytorch 2.1 and CUDA 12. In particular:
|
I am using the changes to CMakeLists.txt as a patch to build this conda-forge/nnpops-feedstock#29 |
@mikemhenry I would like to merge this, but I believe the self hosted runner is not working. |
Compiling with CUDA 12 and a very recent pytorch version (such as v2.1.0 from the nightly) will make compilation fail because C++17 is required to compile pytorch:
Simply setting the standard from 14 to 17 in CMakeLists.txt fixes it.
CUDA 11 also supports C++17, but CUDA 10.2 does not. I check for this and leave it at C++14 in that case.
GCC supports C++17 since version 7, so I default it to it.