Displaying 5 results from an estimated 5 matches for "c_file_using_llvm".
2005 May 17
2
[LLVMdev] Scheme + LLVM JIT
...t 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 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.
--
-Alex
2005 May 17
0
[LLVMdev] Scheme + LLVM JIT
...ry 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 ou...
2005 May 17
1
[LLVMdev] Scheme + LLVM JIT
...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...
2005 May 16
0
[LLVMdev] Scheme + LLVM JIT
On Fri, 13 May 2005, Alexander Friedman wrote:
>>> This requires being able to parse strings. The LLVM 'Parser.h' interface
>>> (and implementation) has the built in assumptions that it will always be
>>> parsing from the file system. Would you guys accept a patch that makes
>>> it more general (ie, parse from file or string)?
>>
>> Yes,
2005 May 13
3
[LLVMdev] Scheme + LLVM JIT
> > This requires being able to parse strings. The LLVM 'Parser.h' interface
> > (and implementation) has the built in assumptions that it will always be
> > parsing from the file system. Would you guys accept a patch that makes
> > it more general (ie, parse from file or string)?
>
> Yes, that's a generally useful thing to have, I'd like to see it