aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
diff options
context:
space:
mode:
authorAlex Langford <alangford@apple.com>2023-07-25 15:38:04 -0700
committerAlex Langford <alangford@apple.com>2023-07-25 15:52:33 -0700
commita809720102fae8d1b5a7073f99f9dae9395c5f41 (patch)
tree44169dd0b1edf6661e1c2d7de02805167d726289 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
parent03399a928ff09aa7030cbab39ddafb5f78880f42 (diff)
downloadllvm-a809720102fae8d1b5a7073f99f9dae9395c5f41.zip
llvm-a809720102fae8d1b5a7073f99f9dae9395c5f41.tar.gz
llvm-a809720102fae8d1b5a7073f99f9dae9395c5f41.tar.bz2
[lldb][NFCI] Change logic to find clang resource dir in standalone builds
As of 0beffb854209a41f31beb18f9631258349a99299 there is a CMake function to actually calculate the relative path to the clang resource directory. Currently we have some bespoke logic that looks in a few places, but with this new function we should be able to eliminate some complexity here. Also, I moved the functionality from LLDBConfig to LLDBStandalone since it is only used in standalone builds. Differential Revision: https://reviews.llvm.org/D156270
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions