search for: findmodulesdefiningsymbols

Displaying 4 results from an estimated 4 matches for "findmodulesdefiningsymbols".

2013 Dec 20
2
[LLVMdev] [LLVM] What has happened to LLVM bitcode archive support?
Hi Rafael and other LLVM devs, I'm currently upgrading a project that uses LLVM that links a bitcode archive (a C library) with a module. Originally we used Linker::LinkInFile() but that was removed by r172749. So I started looking for an alternative and I found Archive::findModulesDefiningSymbols() which looked very promising as it would allow me to very easily implement linking a bitcode archive with a module efficiently (i.e. only call Linker::LinkModules() on the relevant bitcode modules inside the bitcode archive). Before I started I thought I'd better check that this API was still...
2013 Dec 20
0
[LLVMdev] [LLVM] What has happened to LLVM bitcode archive support?
...ael and other LLVM devs, > > I'm currently upgrading a project that uses LLVM that links a bitcode > archive (a C library) with a module. Originally we used > Linker::LinkInFile() but that was removed by r172749. So I started > looking for an alternative and I found > Archive::findModulesDefiningSymbols() which looked very promising as > it would allow me to very easily implement linking a bitcode archive > with a module efficiently (i.e. only call Linker::LinkModules() on the > relevant bitcode modules inside the bitcode archive). > > Before I started I thought I'd better check...
2013 Dec 20
1
[LLVMdev] [LLVM] What has happened to LLVM bitcode archive support?
...>> >> I'm currently upgrading a project that uses LLVM that links a bitcode >> archive (a C library) with a module. Originally we used >> Linker::LinkInFile() but that was removed by r172749. So I started >> looking for an alternative and I found >> Archive::findModulesDefiningSymbols() which looked very promising as >> it would allow me to very easily implement linking a bitcode archive >> with a module efficiently (i.e. only call Linker::LinkModules() on the >> relevant bitcode modules inside the bitcode archive). >> >> Before I started I thought...
2014 Jun 04
3
[LLVMdev] Module::getOrInsertFunction determinism
Hi Philip, Thank you very much for your comments. I think I’ve discovered a root cause. The problem was in linking bit code archive files with the module. At some point, std::set<Module*> is used and iterated over. I believe this was the reason why e.g. It worked consistently with ASLR turned off and produced non-deterministic output otherwise. I changed that bit to use vector instead and