Steven Wu feb609a738 [ThinLTO] Adding architecture name into saved object filename ... 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		2019-04-29 21:39:54 +00:00
..
Caching.cpp
CMakeLists.txt
LLVMBuild.txt
LTO.cpp	[LTO] Add plumbing to save stats during LTO on Darwin.	2019-04-19 12:36:41 +00:00
LTOBackend.cpp	[NewPassManager] Adding pass tuning options: loop vectorize.	2019-04-19 16:11:59 +00:00
LTOCodeGenerator.cpp	[LTO] Add plumbing to save stats during LTO on Darwin.	2019-04-19 12:36:41 +00:00
LTOModule.cpp
SummaryBasedOptimizations.cpp
ThinLTOCodeGenerator.cpp	[ThinLTO] Adding architecture name into saved object filename	2019-04-29 21:39:54 +00:00
UpdateCompilerUsed.cpp