search for: fib_funct

...struct backed by a string? FYI, here is a sketch of what the fib example would look like: #include "llvm_c.h" /* Everything takes and recieves void * pointers. This to avoid redefining C++ types. This is the C 'version' of the Fib example, at least in spirit. */ char* fib_function = "int %fib (int %AnArg) {" " EntryBlock: " " %cond = setle int AnArg, 2" " branch bool %cond, label return, label recur" " return:" " ret int 1" " recur:" " %sub1 = sub int %AnArg, 1" " %fibx1 = cal...

...t the fib example would look like: > > #include "llvm_c.h" > > /* > Everything takes and recieves void * pointers. This to avoid redefining C++ > types. Makes sense. > This is the C 'version' of the Fib example, at least in spirit. > */ > > char* fib_function = > "int %fib (int %AnArg) {" > > " EntryBlock: " > " %cond = setle int AnArg, 2" > " branch bool %cond, label return, label recur" > > " return:" > " ret int 1" > > " recur:" > " %sub1 =...

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

> 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

...gs 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... Name: asm_parser.diff Type: application/octet-stream Size: 9012 bytes De...