search for: llvm_addpass

...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()); // add optimization passes here // addPass (PM, ... ) llvm_run_passes(PM,M); // merge modules - not relevant here // make an execution engine from the module void * JE = llvm_make_jit_engine (M); // ge...

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

...xt (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 > llvm_addPass(PM, make_target_data("jit-lib",M)); > > llvm_addPass (PM, llvm_createVerifierPass()); I'd suggest using C style llvm_create_verifier_pass consistently, but your call :) > // add optimization passes here > // addPass (PM, ... ) > > llvm_run_passes(PM,M); > >...

> 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