Steven Wu 0298cbfe6d [LTO] Don't apply LTOPostLink module flag during writeMergedModule ... For `ld64` which uses legacy LTOCodeGenerator, it relies on writeMergedModule to perform `ld -r` (generates a linked object file). If all the inputs to `ld -r` is fullLTO bitcode, `ld64` will linked the bitcode module, internalize all the symbols and write out another fullLTO bitcode object file. This bitcode file doesn't have all the bitcode inputs and it should not have LTOPostLink module flag. It will also cause error when this bitcode object file is linked with other LTO object file. Fix the issue by not applying LTOPostLink flag during writeMergedModule function. The flag should only be added when all the bitcode are linked and ready to be optimized. rdar://problem/58462798 Reviewed By: tejohnson Differential Revision: https://reviews.llvm.org/D84789		2020-08-26 11:17:45 -07:00
..
CMakeLists.txt	Replace MCTargetOptionsCommandFlags.inc and CommandFlags.inc by runtime registration	2020-03-17 14:01:30 +01:00
llvm-lto.cpp	[LTO] Don't apply LTOPostLink module flag during writeMergedModule	2020-08-26 11:17:45 -07:00
LLVMBuild.txt	Update the file headers across all of the LLVM projects in the monorepo	2019-01-19 08:50:56 +00:00