search for: classllvm_1_1link

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

Did you mean: classllvm_1_1linker
2013 Dec 17
3
[LLVMdev] How to do bitcode archive linking correctly?
...an having to invoke an external program (i.e. my system's linker). - For "forthcoming LLVM linker", is that referring to lld [4]? [1] https://github.com/MartinNowack/klee/blob/51d4a2b34511a8d6b00b16a50f90b0bc1a793a69/lib/Module/ModuleUtil.cpp#L61 [2] http://llvm.org/docs/doxygen/html/classllvm_1_1Linker.html#a244da8c7e9789b1b675b9741bd692c63 [3] http://llvm.org/docs/GoldPlugin.html [4] http://lld.llvm.org/ [5] https://github.com/ccadar/klee-uclibc/tree/klee_0_9_29 Thanks, Dan Liew.
2013 Dec 17
0
[LLVMdev] How to do bitcode archive linking correctly?
...an external program (i.e. my system's linker). > - For "forthcoming LLVM linker", is that referring to lld [4]? > > [1] https://github.com/MartinNowack/klee/blob/51d4a2b34511a8d6b00b16a50f90b0bc1a793a69/lib/Module/ModuleUtil.cpp#L61 > [2] http://llvm.org/docs/doxygen/html/classllvm_1_1Linker.html#a244da8c7e9789b1b675b9741bd692c63 > [3] http://llvm.org/docs/GoldPlugin.html > [4] http://lld.llvm.org/ > [5] https://github.com/ccadar/klee-uclibc/tree/klee_0_9_29 > > Thanks, > Dan Liew. > _______________________________________________ > LLVM Developers mailing li...
2018 May 16
1
LLVM JIT 3.9 vs 6.0: How to emitAndFinalize multiple modules correctly?
Hi all, I am having hard time figuring out how I should use the API for JIT in LLVM 6. In LLVM 3.9 I am used to adding all objects at once and emitAndFinalizing them all: handle = objectLayer.addObjectSet(objectFiles, memoryManager, resolver); objectLayer.emitAndFinalize(handle); In LLVM 6.0 the objects are added one by one: auto handle = objectLayer.addObject(objectFile, resolver).get();
2013 Feb 14
1
[LLVMdev] multiple LLVMContext or just one?
On Feb 13, 2013, at 17:26 , Lang Hames <lhames at gmail.com> wrote: > LLVMContext was designed to support multithreading by holding the compilation context for each thread in a separate LLVMContext. If you're building modules in parallel you definitely need one LLVMContext per thread. > > If you're talking about compiling multiple modules sequentially with a single context