-
Notifications
You must be signed in to change notification settings - Fork 7.2k
Move cmake_[windows|linux]_gpu to CUDA-11.3 #4920
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
Conversation
💊 CI failures summary and remediationsAs of commit b604bf9 (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
1d75997
to
00b8229
Compare
00b8229
to
e0ff4a7
Compare
set "CUDA_PATH_V%CUDA_VER_MAJOR%_%CUDA_VER_MINOR%=%ProgramFiles%\NVIDIA GPU Computing Toolkit\CUDA\v%CUDA_VERSION_STR%" | ||
set "NVTOOLSEXT_PATH=%ProgramFiles%\NVIDIA Corporation\NvToolsExt\bin\x64" | ||
|
||
if not exist "%ProgramFiles%\NVIDIA GPU Computing Toolkit\CUDA\v%CUDA_VERSION_STR%\bin\nvcc.exe" ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we move this section to line 195
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds like a good idea. Let me do it as part of separate PR
e0ff4a7
to
13d15e6
Compare
@malfet , errorlevel would be non-zero if setup.exe failed.
|
|
13d15e6
to
b862f00
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@malfet Thanks for your help in fixing this. I've added a couple of questions, let me know your thoughts.
CMakeLists.txt
Outdated
cmake_minimum_required(VERSION 3.12) | ||
project(torchvision) | ||
set(CMAKE_CXX_STANDARD 14) | ||
set(CMAKE_CXX_STANDARD 17) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this necessary? My understanding is that TorchVision aligns with PyTorch
s approach and sets CMAKE_CXX_STANDARD
to 14.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is necessary to fix Windows compilation errors, where CUDA-11.x (which supports C++17 standard) could not be compiled using C++14 standard.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification. Makes sense. So I guess PyTorch Core will be moving as well to C++17, right?
b862f00
to
8a6713c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Summary: * Set cuversion to 113 for cmake builds * Build CUDA-11 Windows cmake using C++17 * Cherry-pick pkg_helper changes from pytorch/audio back to vision Reviewed By: datumbox Differential Revision: D32470469 fbshipit-source-id: a40cbebb7d11ff4af08faa3c65d1a5d929652461 Co-authored-by: Vasilis Vryniotis <datumbox@users.noreply.github.com>
Also, made a small change to CUDA install script on windows:
echo %errorlevel%
would always return 0, and save cuda install log into the home folder rather than in current directorycc @seemethere