aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.cpp
diff options
context:
space:
mode:
authorYe Luo <yeluo@anl.gov>2024-05-22 09:40:43 -0500
committerGitHub <noreply@github.com>2024-05-22 09:40:43 -0500
commit831d1435193e73026e03e006a5b86591f3d202b3 (patch)
tree7e6481ea01d8c1ba090f36323423b8bd3ba2b73f /lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.cpp
parent183beb33d7f8847c04870e425d75f27db1cf5847 (diff)
downloadllvm-831d1435193e73026e03e006a5b86591f3d202b3.zip
llvm-831d1435193e73026e03e006a5b86591f3d202b3.tar.gz
llvm-831d1435193e73026e03e006a5b86591f3d202b3.tar.bz2
[Offload] libomptarget force dlopen vendor libraries by default. (#92788)
Since #87009, libomptarget directly links all the plugins statically. All the dependencies of plugins got exposed to libomptarget. The CUDA plugin depends on libcuda and the amdgpu plugin depends on libhsa if not forced using dlopen. On a cluster with different compute node architectures, libomptarget can be built and run on different nodes. In the build stage, if cmake founds libcuda and `LIBOMPTARGET_FORCE_DLOPEN_LIBCUDA=OFF`, libomptarget links libcuda.so directly and the result libomptarget may not run a node without a NVIDIA driver for example a CPU or AMD GPU only machine with a complaint that libcuda.so not found. The solution is setting `LIBOMPTARGET_FORCE_DLOPEN_LIBCUDA` and `LIBOMPTARGET_FORCE_DLOPEN_LIBHSA` `ON`. Preferably this should be default to maximize the usability of libomptarget. If cmake detects NVIDIA or AMD software on an OS imaging building node, the resulted libomptarget may not be able to function on the user side due to the requirement the existence of vendor runtime libraries.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.cpp')
0 files changed, 0 insertions, 0 deletions