Displaying 5 results from an estimated 5 matches for "llvm_make_module_from_text".
2005 May 12
2
[LLVMdev] Scheme + LLVM JIT
...ot;
" %sub1 = sub int %AnArg, 1"
" %fibx1 = call tail int %fib (int %sub1) "
" %sub2 = sub int %AnArg, 2"
" %fibx2 = call tail int %fib (int %sub2) "
" %result = add int %fibx1, %fibx2"
" ret int %result"
"}";
void * M = llvm_make_module_from_text (program, "test") ;
// now we want to run some optimizations on this thing.
// make a pass manager
void * PM = llvm_make_pass_manager();
// add 'target data' to module
llvm_addPass(PM, make_target_data("jit-lib",M));
llvm_addPass (PM, llvm_createVerifierPass());
// a...
2005 May 13
0
[LLVMdev] Scheme + LLVM JIT
...uot;
> " %fibx2 = call tail int %fib (int %sub2) "
> " %result = add int %fibx1, %fibx2"
> " ret int %result"
> "}";
Some typeos (branch -> br, 'call tail' -> 'tail call', etc) but general
idea makes sense.
> void * M = llvm_make_module_from_text (program, "test") ;
One of these should be fib_function right? What is the 'test' string?
> // now we want to run some optimizations on this thing.
> // make a pass manager
> void * PM = llvm_make_pass_manager();
>
> // add 'target data' to module
> ll...
2005 May 10
0
[LLVMdev] Scheme + LLVM JIT
On Thu, 5 May 2005, Alexander Friedman wrote:
>>> Does there happen to be a C interface to the jit ? Our scheme impl
>>> has a good FFI, but it doesn't do C++. If not, this is no big deal,
>>> and i'll just write something myself.
>>
>> No, but such bindings would be *very useful*. And since there might be
>> other people who need them this
2005 May 05
3
[LLVMdev] Scheme + LLVM JIT
> So as it stands, one should think of out JIT as something akin to the
> early Java JITs: one function at a time and only one compile per
> function. This is extremely primative by modern JIT standards, where a
> JIT will do profiling, find hot functions and reoptimize them,
> reoptimize functions when more information about the call tree is
> available, have several levels of
2005 May 13
3
[LLVMdev] Scheme + LLVM JIT
...o remove those lines completely if they
are in fact not.
I havn't tested parsing strings yet. My code is extremely simple and
*should* work, but we know where that line of thinking leads. Should I
submit a test case (it would have to be a C file that links in the
parser)?
> > void * M = llvm_make_module_from_text (program, "test") ;
>
> One of these should be fib_function right? What is the 'test' string?
In the fib example, the module is named 'test', so I assumed it was
usefull for some reason.
-------------- next part --------------
A non-text attachment was scrubbed.....