Displaying 3 results from an estimated 3 matches for "indygreg".
Did you mean:
indexreg
2012 Mar 19
0
[LLVMdev] Python bindings in tree
...gt; LLVMDumpModule but dumps to a string instead of stdout.
>
> * 0005-Add-LLVMCreateMemoryBufferFromData-to-llvm-c.patch
> Adds LLVMCreateMemoryBufferFromData function.
These are desperately needed by the C API. Can you please submit them?
FWIW, all my work is at
https://github.com/indygreg/llvm/tree/python_bindings/bindings/python.
Parts of Core.h still need love (especially the Value system). I'm doing
some dynamic type creation at run-time using the Value hierarchy.
Somewhat scary stuff, but it does seem to work. I really need a
LLVMGetValueID() API to fetch llvm::Value::getVal...
2012 Mar 17
3
[LLVMdev] Python bindings in tree
At Fri, 16 Mar 2012 14:12:08 +0100,
Christoph Grenz wrote:
>
> 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
>
2012 Mar 19
2
[LLVMdev] Python bindings in tree
...stead of stdout.
> >
> > * 0005-Add-LLVMCreateMemoryBufferFromData-to-llvm-c.patch
> > Adds LLVMCreateMemoryBufferFromData function.
>
> These are desperately needed by the C API. Can you please submit them?
Will do!
> FWIW, all my work is at
> https://github.com/indygreg/llvm/tree/python_bindings/bindings/python.
Excellent! I'll try to see if I can adapt my bindings to your to fill
in the gaps.
There do indeed seem to be much overlap in our bindings. But there are
a few things where the design differs. If we should try to combine our
work I guess it would be...