Jeffrey Yasskin fb10587e50 Kill ModuleProvider and ghost linkage by inverting the relationship between ... Modules and ModuleProviders. Because the "ModuleProvider" simply materializes GlobalValues now, and doesn't provide modules, it's renamed to "GVMaterializer". Code that used to need a ModuleProvider to materialize Functions can now materialize the Functions directly. Functions no longer use a magic linkage to record that they're materializable; they simply ask the GVMaterializer. Because the C ABI must never change, we can't remove LLVMModuleProviderRef or the functions that refer to it. Instead, because Module now exposes the same functionality ModuleProvider used to, we store a Module* in any LLVMModuleProviderRef and translate in the wrapper methods. The bindings to other languages still use the ModuleProvider concept. It would probably be worth some time to update them to follow the C++ more closely, but I don't intend to do it. Fixes http://llvm.org/PR5737 and http://llvm.org/PR5735. llvm-svn: 94686		2010-01-27 20:34:15 +00:00
..
ADT	Add a SmallBitVector class, which mimics BitVector but uses only	2010-01-05 15:04:49 +00:00
ExecutionEngine	Kill ModuleProvider and ghost linkage by inverting the relationship between	2010-01-27 20:34:15 +00:00
Support	Fix TimeValue::now() on Unix.	2010-01-22 15:51:31 +00:00
Transforms	Factor out redundancy from clone() implementations.	2009-10-27 22:16:29 +00:00
VMCore	Roll r94484 (avoiding RTTI problems in tests) forward again in a way that isn't	2010-01-26 23:30:46 +00:00
Makefile	New unit test for the cloning module, which so far only covers cloning of	2009-09-27 21:39:46 +00:00
Makefile.unittest	Roll r94484 (avoiding RTTI problems in tests) forward again in a way that isn't	2010-01-26 23:30:46 +00:00