aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2021-04-21 13:59:54 -0700
committerJonas Devlieghere <jonas@devlieghere.com>2021-04-21 14:22:13 -0700
commit6331680ad2ad000fdaf7e72f3c1880c7908ffa25 (patch)
treed0f8102ee21e74fb0ddb9f38880288723e288933 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
parent5a2d78b1639738fbde85248413c1cfd2df55683a (diff)
downloadllvm-6331680ad2ad000fdaf7e72f3c1880c7908ffa25.zip
llvm-6331680ad2ad000fdaf7e72f3c1880c7908ffa25.tar.gz
llvm-6331680ad2ad000fdaf7e72f3c1880c7908ffa25.tar.bz2
Re-land "[Driver] Support default libc++ library location on Darwin"
This reverts commit 05eeed9691aeb3e0316712195b998e9078cdceb0 and after fixing the impacted lldb tests in 5d1c43f333c2327be61604dc90ea675f0d1e6913. [Driver] Support default libc++ library location on Darwin Darwin driver currently uses libc++ headers that are part of Clang toolchain when available (by default ../include/c++/v1 relative to executable), but it completely ignores the libc++ library itself because it doesn't pass the location of libc++ library that's part of Clang (by default ../lib relative to the exceutable) to the linker always using the system copy of libc++. This may lead to subtle issues when the compilation fails because the headers that are part of Clang toolchain are incompatible with the system library. Either the driver should ignore both headers as well as the library, or it should always try to use both when available. This patch changes the driver behavior to do the latter which seems more reasonable, it makes it easy to test and use custom libc++ build on Darwin while still allowing the use of system version. This also matches the Clang driver behavior on other systems. Differential Revision: https://reviews.llvm.org/D45639
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions