search for: relocatablecode

...;return:\n" " ret int 1\n" "recur:\n" " %sub1 = sub int %AnArg, 1\n" " %result = tail call fastcc int %foo-int (int %sub1)\n" " ret int %result\n" "}\n" Module * M = parseAsmText(countdown_function); RelocatableCode * code = compileModule(M); WriteRelocatableCodeToFile (code,"file"); // now load. This part should be as light as possible - that is, very small // in size of the compiled binary. The resulting "module" is fairly static, not like // standard llvm modules. // should...

Alexander, Yes, a patch like that would be accepted. Fewer dependencies = good :) Some notes on doing this: (1) Please make sure you use the std c++ iostream libraries for doing I/O. No native calls (we end up with portability problems). If you need something that must be ported, please add it to lib/System (2) You should also use the sys::Path class (include/llvm/System/Path.h) for handling

On May 16, Chris Lattner wrote: > On Mon, 16 May 2005, Alexander Friedman wrote: > > Would it be possible (ie, relatively straitforward) to do the > > following: Take the code in module A, compile it with the JIT (since > > we cannot make libraries in Windows), and save the resulting binary > > goo in some file. Later (in a different instance of the runtime), with >

...; "recur:\n" > " %sub1 = sub int %AnArg, 1\n" > " %result = tail call fastcc int %foo-int (int %sub1)\n" > " ret int %result\n" > "}\n" > > > Module * M = parseAsmText(countdown_function); > > RelocatableCode * code = compileModule(M); > > WriteRelocatableCodeToFile (code,"file"); > > // now load. This part should be as light as possible - that is, very small > // in size of the compiled binary. The resulting "module" is fairly static, not like > // standa...