aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineCopyPropagation.cpp
diff options
context:
space:
mode:
authorJoseph Huber <jhuber6@vols.utk.edu>2022-05-16 11:49:51 -0400
committerJoseph Huber <jhuber6@vols.utk.edu>2022-05-16 18:18:32 -0400
commit5ffecd28c9fb3098049f0477759f779122153499 (patch)
treea9156e258bff4da1993b783a0cb5e97bb21a240d /llvm/lib/CodeGen/MachineCopyPropagation.cpp
parent18fc39590978949fb75969e4bd63f8d2f13288ad (diff)
downloadllvm-5ffecd28c9fb3098049f0477759f779122153499.zip
llvm-5ffecd28c9fb3098049f0477759f779122153499.tar.gz
llvm-5ffecd28c9fb3098049f0477759f779122153499.tar.bz2
[Libomptarget] Don't build the device runtime without a new Clang
The OpenMP device offloading library is a bitcode library and thus only expect to build and linked with the same version of clang that was used to create it. This somewhat copmlicates the building process as we require the Clang that was just built to be used to create the library. This is either done with a two-step build, where OpenMP is built with the Clang that was just installed, or through the `-DLLLVM_ENABLE_RUNTIMES=openmp` option. This has always been the case, but recent changes have caused this to make it difficult to build the rest of OpenMP. This patchs adds a check to not build the OpenMP device runtime if the current compiler is not Clang with the same version as the LLVM installation. This should allow users to build OpenMP as a project using any compiler without it erroring out due to the bitcode library, but if users require it they will need to use the above methods to compile it. Reviewed By: jdoerfert, tianshilei1992, ye-luo Differential Revision: https://reviews.llvm.org/D125698
Diffstat (limited to 'llvm/lib/CodeGen/MachineCopyPropagation.cpp')
0 files changed, 0 insertions, 0 deletions