hahnjo wrote: > We had a lot that were like this previously. Guessing this one slipped > through because of the `zlib` requirement.
I actually think there are some more left; for example `clang/test/Driver/cuda-dwarf-2.cu` has many `not %clang` invocations that don't specify `--cuda-path`. This happens to work on my system because my CUDA installation is too recent to support `sm_20`, but I suspect it would actually fail with an older CUDA installed... > Does this work with `-nogpulib` instead? Usually easier than passing the > dummy CUDA path. It definitely doesn't work for the "pure" CUDA invocations, it still finds my local installation and complains. It might work for the OpenMP invocations, but hard to tell for me on a system with CUDA installed. As it's a `.cu` test after all, I think I would prefer the uniformity of passing `--cuda-path` everywhere and be safe from any weird interaction. https://github.com/llvm/llvm-project/pull/84008 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
