Teresa Johnson 525ee88977 [ThinLTO] Import local variables from the same module as caller ... Summary: We can sometimes end up with multiple copies of a local variable that have the same GUID in the index. This happens when there are local variables with the same name that are in different source files having the same name/path at compile time (but compiled into different bitcode objects). In this case make sure we import the copy in the caller's module. This enables importing both of the variables having the same GUID (but which will have different promoted names since the module paths, and therefore the module hashes, will be distinct). Importing the wrong copy is particularly problematic for read only variables, since we must import them as a local copy whenever referenced. Otherwise we get undefs at link time. Note that the llvm-lto.cpp and ThinLTOCodeGenerator changes are needed for testing the distributed index case via clang, which will be sent as a separate clang-side patch shortly. We were previously not doing the dead code/read only computation before computing imports when testing distributed index generation (like it was for testing importing and other ThinLTO mechanisms alone). Reviewers: evgeny777 Subscribers: mehdi_amini, inglorion, eraman, steven_wu, dexonsmith, dang, llvm-commits Differential Revision: https://reviews.llvm.org/D55047 llvm-svn: 347886		2018-11-29 17:02:42 +00:00
..
CMakeLists.txt	[CMake] llvm-lto depends on intrinsics_gen	2016-11-18 23:20:35 +00:00
llvm-lto.cpp	[ThinLTO] Import local variables from the same module as caller	2018-11-29 17:02:42 +00:00
LLVMBuild.txt	Fix library dependency for llvm-lto after r262977	2016-03-09 02:34:13 +00:00