Mehdi Amini d4c7e117aa Remove "ExportingModule" from ThinLTO Index (NFC) ... There is no real reason the index has to have the concept of an exporting Module. We should be able to have one single unique instance of the Index, and it should be read-only after creation for the whole ThinLTO processing. The linker plugin should be able to process multiple modules (in parallel or in sequence) with the same index. The only reason the ExportingModule was present seems to be to implement hasExportedFunctions() that is used by the Module linker to decide what to do with the current Module. For now I replaced it with a query to the map of Modules path to see if this module was declared in the Index and consider that if it is the case then it is probably exporting function. On the long term the Linker interface needs to evolve and this call should not be needed anymore. From: Mehdi Amini <mehdi.amini@apple.com> git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@254581 91177308-0d34-0410-b5e6-96231b3b80d8		2015-12-03 02:37:23 +00:00
..
BitcodeReader.cpp	Remove "ExportingModule" from ThinLTO Index (NFC)	2015-12-03 02:37:23 +00:00
BitReader.cpp	Return a unique_ptr from getLazyBitcodeModule and parseBitcodeFile. NFC.	2015-06-16 22:27:55 +00:00
BitstreamReader.cpp	[BitstreamReader] Make sure the Array operand type is an encoding	2015-05-27 00:48:43 +00:00
CMakeLists.txt	Use ADDITIONAL_HEADER_DIRS in all LLVM CMake projects.	2015-02-11 03:28:02 +00:00
LLVMBuild.txt
Makefile