Hahnfeld added a comment.
Herald added a subscriber: dexonsmith.
Herald added a project: LLVM.
@tra The split between `LATEST` and `LATEST_SUPPORTED` leads to very weird
warning and error messages:
clang-14: warning: unknown CUDA version: cuda.h: CUDA_VERSION=11040.;
assuming the latest supported version 10.1 [-Wunknown-cuda-version]
clang-14: error: cannot find libdevice for sm_20; provide path to different
CUDA installation via '--cuda-path', or pass '-nocudalib' to build without
linking with libdevice
clang-14: error: GPU arch sm_20 is supported by CUDA versions between 7.0 and
8.0 (inclusive), but installation at /usr/local/cuda-11.4 is 11.2; use
'--cuda-path' to specify a different CUDA install, pass a different GPU arch
with '--cuda-gpu-arch', or pass '--no-cuda-version-check'
Clang is mentioning three different CUDA versions here: 11.4 is what I really
have installed, 11.2 is `LATEST` and therefore the one returned by
`getCudaVersion` or as the "last resort" in `CudaInstallationDetector`, and the
first warning says that Clang assumes the latest supported version 10.1. As a
developer looking into the code, I get that the first warning is about saying
that 10.1 is the latest fully supported version in terms of features, but I
think this is really confusing to users. Do you see a chance to improve this?
(other than adding just 11.3 and 11.4 to the enumerations where we'll always
run behind)
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D77670/new/
https://reviews.llvm.org/D77670
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
