forked from OSchip/llvm-project
6c9f6fd11b
Summary: For ThinLTOCodegenerator, it has an option to save the object file outputs into a directory which is essential for debug info. Tools like lldb and dsymutil will look for these object files for debug info. On Darwin platform, you can link fat binaries with one single clang driver invocation like: $ clang -arch x86_64 -arch i386 -Wl,-object_path_lto,$TMPDIR ... Unfornately, the output object files for one architecture is going to overwrite the previous ones and one architecture slice will end up with no debug info. One example for this is to turn on ThinLTO for sanitizer dylibs in compiler-rt project. To fix the issue, add the name for the architecture into the name of the output object file. rdar://problem/35482935 Reviewers: tejohnson, bd1976llvm, dexonsmith, JDevlieghere Reviewed By: dexonsmith Subscribers: mehdi_amini, aprantl, inglorion, eraman, hiraditya, jkorous, dang, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D60924 llvm-svn: 359508 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| Caching.cpp | ||
| LLVMBuild.txt | ||
| LTO.cpp | ||
| LTOBackend.cpp | ||
| LTOCodeGenerator.cpp | ||
| LTOModule.cpp | ||
| SummaryBasedOptimizations.cpp | ||
| ThinLTOCodeGenerator.cpp | ||
| UpdateCompilerUsed.cpp | ||