Mehdi Amini 07b85fee55 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> llvm-svn: 254581		2015-12-03 02:37:23 +00:00
..
Reader	Remove "ExportingModule" from ThinLTO Index (NFC)	2015-12-03 02:37:23 +00:00
Writer	[ThinLTO] Add MODULE_CODE_METADATA_VALUES record	2015-11-20 14:51:27 +00:00
CMakeLists.txt
LLVMBuild.txt
Makefile
module.modulemap	[modules] Add module maps for LLVM. These are not quite ready for prime-time	2014-05-21 02:46:14 +00:00