[LLVMdev] Scheme + LLVM JIT
Alexander Friedman
alex at inga.mit.edu
Mon May 16 21:18:31 PDT 2005
On May 16, Chris Lattner wrote:
> > This seems reasonable, but what happens to the users of the module if
> > it were to be updated - for example, if I load said module in the jit,
> > and then add something to it.
>
> This should be fine. The JIT won't touch a function until it is called.
What if you read in a function with the same signature? Will it just
replace it?
> > About the linking. Is it possible (within the current makefile
> > framework) to create a shared library that (statically) contains some
> > set of llvm libraries (including the JIT, which currenlty only works
> > if building a tool).
>
> I don't know. It seems possible: each library can be built as a .so file
> individually. Each directory can also be relinked into a single .o file.
> It seems logical that you could take these .o files and make a .so file :)
>
> > I wish to be able to do the following, assuming that I named that
> > library LLVM_C
> >
> > gcc -lc -lLLVM_C c_file_using_llvm.c -I<stuff> -L<stuff>
> >
> > I *could* build everything as a shared library, and include everything
> > on the command line that way, but that seems a bit errorprone, not to
> > mention the fact that building everything with PIC takes ~3x longer.
>
> This should be possible, though our current makefile system is not going
> to do this automatically right now.
Can I add submit a patch to do something like this (if it doesn't
disturb the makefile system that much)?
Maybe if one is building a library and sets a "LINK_IN_LIBS" flag or
something? I am guessing there might be other people that want
something like this - ie, anybody building a shared library that they
want to use in another application.
--
-Alex
More information about the llvm-dev
mailing list