forked from OSchip/llvm-project
9b3baaa74a
https://reviews.llvm.org/D25932 made it so that clang always checks if libLTO.dylib is present on disk, even if -flto is not being used. The motivation for that change was that if a dependency happens to contain bitcode, ld64 will try to load libLTO without -flto explicitly being enabled. However, the change had the undesirable side effect of warning if libLTO.dylib doesn't exist even if it isn't needed. Change things so that -lto_library is always passes, independent of if it exists or not. ld64 only looks at this flag if it uses LTO. If the dylib exists, all is well. If it doesn't, and LTO is not being used, all is well too. If ld64 does end up using LTO and the dylib does not exist, ld64 will print something like ld: could not process llvm bitcode object file, because foo/libLTO.dylib could not be loaded file 'test.o' for architecture x86_64 https://reviews.llvm.org/D26984 llvm-svn: 287685 |
||
|---|---|---|
| .. | ||
| Action.cpp | ||
| CMakeLists.txt | ||
| Compilation.cpp | ||
| CrossWindowsToolChain.cpp | ||
| Driver.cpp | ||
| DriverOptions.cpp | ||
| InputInfo.h | ||
| Job.cpp | ||
| MSVCToolChain.cpp | ||
| MinGWToolChain.cpp | ||
| Multilib.cpp | ||
| Phases.cpp | ||
| SanitizerArgs.cpp | ||
| Tool.cpp | ||
| ToolChain.cpp | ||
| ToolChains.cpp | ||
| ToolChains.h | ||
| Tools.cpp | ||
| Tools.h | ||
| Types.cpp | ||