search for: bitcode_size

...code using "clang++ -S --emit-llvm", then create a .cpp file containing the bitcode, which is compiled into my app. * Before JITing the dynamic code, my app initializes the Module like this: llvm::MemoryBuffer* buf = llvm::MemoryBuffer::getMemBuffer (llvm::StringRef(bitcode, bitcode_size), name); llvm::Module *m = llvm::getLazyBitcodeModule (buf, context(), err); where bitcode is a big char array holding the precompiled bitcode. The idea is to "seed" the module with that precompiled bitcode so that any calls I inserted into the IR will work properly. * When I...

> It is simpler. There is not any Mach-O envelope. The platform linker > can directly read Mach-O files as well as llvm bit-code file (using > llvm bit-code file reader). > > > Not sure if/where the exact form of the Mach-O file that carries bit > > code is documented. Thanks for that. Yes, I see what you mean (no Mach-O envelope), yet there seems to be something

> Aaah. Wasn't quite sure what you were doing here. I'm not positive > what llvm can emit via the writers (there's support for all parts of > the file format), but it could be extended to write one out. I'm just > not quite sure why :) > > -eric Well, ultimately I'm curious about what it would take to port a JVM based language (http://openquark.org) to