Displaying 2 results from an estimated 2 matches for "059448".
Did you mean:
59448
2013 Dec 17
0
[LLVMdev] How to do bitcode archive linking correctly?
...'t
> right. So what is the right way to programmatically link in LLVM
> bitcode archives into a bitcode module?
>
What we are using in Mesa is pretty similar to what you are doing in
[1]. Take a look at this mailing list post:
http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-February/059448.html
and also the change we made in Mesa as a result of this commit:
http://cgit.freedesktop.org/mesa/mesa/commit/src/gallium/state_trackers/clover/llvm/invocation.cpp?id=aa1c734b3ca445b5af743b9bad6a48ca7ba21f3c
for some background on this linker change.
For the implementation details of Linker::L...
2013 Dec 17
3
[LLVMdev] How to do bitcode archive linking correctly?
Hi,
We're currently upgrading KLEE to work with LLVM >=3.3 and we've hit a problem.
It seems r172749 removed support for linking a bitcode archive into a
module. KLEE unfortunately depends on this to link in its runtime (
which amongst other things provides a C library [5] ).
A first attempt at linking in a bitcode archive ourselves can be seen in [1].
This approach does not work