Consider LIBRARY_PATH when selecting library paths for NVPTX targets in OpenMP device offloading mode.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
test/Driver/openmp-offload.c | ||
---|---|---|
622 | Will it work on Windows? |
To put it another way, what is special about LIBRARY_PATH in this regard? Do we already pass paths specified with -L? I'm also slightly concerned here with the custom parsing code. Can the logic from tools::addDirectoryList not be reused here?
lib/Driver/ToolChains/Cuda.cpp | ||
---|---|---|
405 | A comment is needed here explaining why this is necessary/desirable. | |
412 | Is this the only use of this variable? How is this not dead code? | |
test/Driver/openmp-offload.c | ||
626 | Can this be a little more specific so that you actually make sure you're getting the offloading linking step here? |
Not needed.
These changes are related to looking up the .bc library for inlining purposes. I believe @arpith-jacob has already handled this in trunk. Therefore this is obsolete code.
A comment is needed here explaining why this is necessary/desirable.