When looking for the bclib Clang considered the default library
path first while it preferred directories in LIBRARY_PATH when
constructing the invocation of nvlink. The latter actually makes
more sense because during development it allows using a non-default
runtime library. So change the search for the bclib to start
looking in directories given by LIBRARY_PATH.
Additionally add a new option --libomptarget-nvptx-path= which
will be searched first. This will be handy for testing purposes.
Details
Diff Detail
- Repository
- rC Clang
Event Timeline
lib/Driver/ToolChains/Cuda.cpp | ||
---|---|---|
670 | Yes, that's explained in the summary. I'll try to see if there is a way to test this, even if we can't expect libomptarget-nvptx to be built together with Clang. At the moment I think only LIBRARY_PATH is tested, I'm adding some for the new --libomptarget-nvptx-path. |
Add const per review comments.
lib/Driver/ToolChains/Cuda.cpp | ||
---|---|---|
670 | After some thoughts it seems impossible to reliably test this code path because the user can set CLANG_LIBDIR_SUFFIX. |
const Arg *A