You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In pursuit of #322 this MR is in progress !463 - in order to use std::filesystem, the C++ standard must be at least 17 with a gcc version of at least 9. These upgrades went smoothly on Deception, as gcc10.2.0 was already used, but Newell is causing problems. https://community.intel.com/t5/Intel-DevCloud/dpcpp-using-C-17-header/m-p/1212280
Now, newell is with gcc10.2.0, c++17 standard - we still get an error with std::fs
see file fs.txt fs.txt
the -lstdc++fs -std=c++17 flags are being correctly passed to gcc and mpic++, but nvcc is using the c++11 standard - this may be our culprit
I tried adding set(CUDA_NVCC_FLAGS "-std=c++17") to the main CMakeLists.txt but that did not seem to pass on the flag correctly.
Commenting out the std::fs lines in the source code with or without the NVCC flag line added causes Umpire to error.
see file nvcc17.txt nvcc17.txt
I fear that umpire6.0.0 may not allow us to use the c++17 standard. #54#56 !463!462 (closed)
In pursuit of #322 this MR is in progress !463 - in order to use std::filesystem, the C++ standard must be at least 17 with a gcc version of at least 9. These upgrades went smoothly on Deception, as gcc10.2.0 was already used, but Newell is causing problems.
https://community.intel.com/t5/Intel-DevCloud/dpcpp-using-C-17-header/m-p/1212280
Now, newell is with gcc10.2.0, c++17 standard - we still get an error with std::fs
see file fs.txt fs.txt
the -lstdc++fs -std=c++17 flags are being correctly passed to gcc and mpic++, but nvcc is using the c++11 standard - this may be our culprit
I tried adding set(CUDA_NVCC_FLAGS "-std=c++17") to the main CMakeLists.txt but that did not seem to pass on the flag correctly.
Commenting out the std::fs lines in the source code with or without the NVCC flag line added causes Umpire to error.
see file nvcc17.txt nvcc17.txt
I fear that umpire6.0.0 may not allow us to use the c++17 standard. #54 #56
!463 !462 (closed)
https://gitlab.pnnl.gov/exasgd/frameworks/exago/-/issues/447
https://gitlab.pnnl.gov/exasgd/frameworks/exago/-/merge_requests/463
The text was updated successfully, but these errors were encountered: