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
CUDA 12 supports C++20 but depends on the host compiler for library features like iterator concepts (I think CCCL trunk's libcu++ might also provide these specifically as cuda::std:: but that is beside the point). At the moment all CUDA versions are installed on top of some old GCC (10.2.0) which doesn't ship these features: Example
CUDA >= 12.4 supports GCC 13 (although there have been some problems with CUDA 12.4.0 concerning GCC 13 prompting fixes in CUDA 12.4.1)
It is possible to change the host compiler (and therefore the standard library, I guess. If I get the right path I would try it out.) using nvcc's -ccbin, but I think it would be cool if each CUDA version on Compiler Explorer would just use the newest supported GCC out of the box.
If the paths to other host compilers were listed (or at least a list of them linked) somewhere in the GUI for easy access usage would be even more flexible as one might want to use e.g. clang++ instead of g++ as host compiler).
Ideally one would have both I guess - better defaults and easier access to paths for customization.
The text was updated successfully, but these errors were encountered:
CUDA 12 supports C++20 but depends on the host compiler for library features like iterator concepts (I think CCCL trunk's libcu++ might also provide these specifically as
cuda::std::
but that is beside the point). At the moment all CUDA versions are installed on top of some old GCC (10.2.0) which doesn't ship these features: ExampleAccording to Spack's internals
It is possible to change the host compiler (and therefore the standard library, I guess. If I get the right path I would try it out.) using nvcc's
-ccbin
, but I think it would be cool if each CUDA version on Compiler Explorer would just use the newest supported GCC out of the box.If the paths to other host compilers were listed (or at least a list of them linked) somewhere in the GUI for easy access usage would be even more flexible as one might want to use e.g. clang++ instead of g++ as host compiler).
Ideally one would have both I guess - better defaults and easier access to paths for customization.
The text was updated successfully, but these errors were encountered: