Displaying 3 results from an estimated 3 matches for "bitlink".
Did you mean:
jitlink
2011 Dec 08
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
...g -shared bar.c -o libbar.so
$ clang foo.c -lbar -L.
$ nm a.out
...
U bar
...
==========================================
Currently, lib/Linker supports first two cases, but not the third. I would
like to be able add this functionality and it even exists as the prototype:
https://github.com/krasin/bitlink
To build, just place it under llvm/tools and register in
tools/CMakefiles.txt
The utility itself is probably not interesting, because it's just a
modified llvm-ld. At the same time, it uses lib/Linker with the added
capability of dynamic linking with bitcode stubs:
$ clang -emit-llvm -c foo.c...
2011 Dec 14
0
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
> Is it more clear now? If not, I would like to give it another try and
> write much more details and examples.
I am still not completely sure I understand the use case. In particular
since you say you want a bitcode module in the end, I don't understand
how this is different from using llvm-link, it doesn't complain about
undefined symbols...
Can you provide an example? What are
2011 Dec 14
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
On Tue, Dec 13, 2011 at 9:27 PM, Rafael Ávila de Espíndola <
rafael.espindola at gmail.com> wrote:
>
> > $ llc bar.bc -filetype=obj -o bar.o
> > $ clang -shared -o bar.so bar.o
> > $ clang -use-gold-plugin foo.o bar.so -o t
> >
> > Is that correct? In particular, "lld t" should show a dependency on
> bar.
> > Any