search for: llvmprintmodul

...contain a few patches to llvm-c. Everything can be found here: http://people.0x63.nu/~andersg/llvm-python-bindings/ * 0001-Fix-class-hierarchy-indentation-in-LLVM_FOR_EACH_VAL.patch * 0029-Trivial-copy-paste-error-in-LangRef.patch These are just cosmetic stuff that I stumbled upon * 0004-Add-LLVMPrintModule-to-llvm-c.patch Adds a new LLVMPrintModule function which is similar to LLVMDumpModule but dumps to a string instead of stdout. * 0005-Add-LLVMCreateMemoryBufferFromData-to-llvm-c.patch Adds LLVMCreateMemoryBufferFromData function. * 0015-LLVMMessageRef.patch Adds a "typedef char *L...

Hello, Am Donnerstag, 15. März 2012, 21:15:02 schrieb Gregory Szorc: > There was some talk on IRC last week about desire for Python bindings to > LLVM's Object.h C interface. So, I coded up some and you can now find > some Python bindings in trunk at bindings/python. Currently, the > interfaces for Object.h and Disassembler.h are implemented. FYI: I recently startet working on

...The automatic generation of the Python ctypes interfaces using the Clang Python bindings is pretty friggin cool! > My local copy also contain a few patches to llvm-c. > > Everything can be found here: > http://people.0x63.nu/~andersg/llvm-python-bindings/ > > > * 0004-Add-LLVMPrintModule-to-llvm-c.patch > Adds a new LLVMPrintModule function which is similar to > LLVMDumpModule but dumps to a string instead of stdout. > > * 0005-Add-LLVMCreateMemoryBufferFromData-to-llvm-c.patch > Adds LLVMCreateMemoryBufferFromData function. These are desperately needed by t...

There was some talk on IRC last week about desire for Python bindings to LLVM's Object.h C interface. So, I coded up some and you can now find some Python bindings in trunk at bindings/python. Currently, the interfaces for Object.h and Disassembler.h are implemented. I'd like to stress that things are still rough around the edges, so use at your own risk. I intend to smooth things over in

...es using the Clang > Python bindings is pretty friggin cool! A nice side effect is that everything is added to the interface. So it is easy to add a small proxy over the lib that shows which parts of the llvm-c API that is exercised by the tests. (have that in my bindings) > > * 0004-Add-LLVMPrintModule-to-llvm-c.patch > > Adds a new LLVMPrintModule function which is similar to > > LLVMDumpModule but dumps to a string instead of stdout. > > > > * 0005-Add-LLVMCreateMemoryBufferFromData-to-llvm-c.patch > > Adds LLVMCreateMemoryBufferFromData function. > &gt...