similar to: [LLVMdev] Wrapping ::print() in LLVM-C.

Hi Mahadevan, This looks very nice. Is there a good reason to maintain this outside of the LLVM source tree, or is this something you would like to see come in tree? - Daniel On Thu, Sep 2, 2010 at 10:58 PM, Mahadevan R <mdevan.foobar at gmail.com> wrote: > Hi all, > > Thought you might be interested: > > llvm-py 0.6 was released a couple of days back. This release is

Hi all, Thought you might be interested: llvm-py 0.6 was released a couple of days back. This release is compatible with LLVM 2.7. Check it out at http://www.mdevan.org/llvm-py/. llvm-py has it's own mailing list, at http://groups.google.com/group/llvm-py. Regards, -Mahadevan. (author of llvm-py)

> Date: Sat, 22 Nov 2008 11:42:49 -0800 > From: Chris Lattner <clattner at apple.com> > Subject: Re: [LLVMdev] [ANN] llvm-py 0.5 released. > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Message-ID: <B7A557A7-587A-478A-AB94-B03FDA6254A8 at apple.com> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > > On Nov 22,

Hi. Version 0.5 of llvm-py, Python bindings for LLVM, has been released. This version supports (only) LLVM 2.4. New instructions of LLVM 2.4 (vicmp, vfcmp, insertvalue, extractvalue) are available. Home page: http://mdevan.nfshost.com/llvm-py/ Feedback welcome. Thanks & Regards, -Mahadevan.

On Tue, Jul 8, 2008 at 12:00 AM, Chris Lattner <sabre at nondot.org> wrote: > On Mon, 7 Jul 2008, Mahadevan R wrote: >> While going through the list of intrinsics in Intrinsics.td, I found >> that it does not match the list given in Language Reference [1]. Does >> this mean that they are not to be used / don't work? Or is it just >> that the documentation is

On Tue, Jun 10, 2008 at 11:07 PM, Mahadevan R <mdevan.foobar at gmail.com> wrote: > int sum(int n) > { > return n + sum(n-1); > } > > it generates this: > > define i32 @sum(i32 %n) nounwind { > entry: > %tmp2 = add i32 %n, -1 ; <i32> [#uses=1] > %tmp3 = tail call i32 @sum( i32 %tmp2 ) nounwind ; <i32>

Hi, The LLVM Assembly Language Reference [1] incorrectly states that the prefix used for dll{import,export} is _imp__; it is actually __imp_. The attached patch fixes this. Thanks & Regards, -Mahadevan. [1] file:///home/mdevan/llvm/docs/LangRef.html#linkage -------------- next part -------------- A non-text attachment was scrubbed... Name: doc-dllimport-prefix.patch Type: text/x-diff Size:

Hi, While playing around on the LLVM, I tried this code: int sum(int n) { if (n == 0) return 0; else return n + sum(n-1); } and this is what "llvm-gcc -O2" gave me: define i32 @sum(i32 %n) nounwind { entry: %tmp215 = icmp eq i32 %n, 0 ; <i1> [#uses=1] br i1 %tmp215, label %bb10, label %tailrecurse.bb10_crit_edge tailrecurse.bb10_crit_edge: ; preds =

On Mon, Jul 7, 2008 at 6:41 PM, Mahadevan R <mdevan.foobar at gmail.com> wrote: > On Tue, Jul 8, 2008 at 12:00 AM, Chris Lattner <sabre at nondot.org> wrote: >> On Mon, 7 Jul 2008, Mahadevan R wrote: >>> While going through the list of intrinsics in Intrinsics.td, I found >>> that it does not match the list given in Language Reference [1]. Does >>>

> Date: Sat, 22 Nov 2008 09:30:09 -0800 > From: Nick Lewycky <nicholas at mxc.ca> > Subject: Re: [LLVMdev] [ANN] llvm-py 0.5 released. > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Message-ID: <492841A1.2040400 at mxc.ca> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Mahadevan R wrote: >> Hi. >> >>

On Fri, Mar 28, 2008 at 12:00 AM, Mahadevan R <mdevan.foobar at gmail.com> wrote: > 1) > Are the C bindings complete? That is, is there some part of the C++ API > that is not exposed by the C API? Nope, there's still a lot that's not done. Patches are always welcome :) We've got enough in subversion to implement the Kaleidoscope tutorial though. > 2) > Do

On Fri, May 16, 2008 at 12:31 PM, Duncan Sands <baldrick at free.fr> wrote: >> > If this is an arbitrary struct, it can be quite tricky. Do you have >> > to worry about bitfields and variable sized fields (for example a >> > variable length array at the end)? What about unions? >> >> There are no bitfields, but it does have a variable length array at

On May 10, 2008, at 05:44, Mahadevan R wrote: > I'd like to announce the availability of Python bindings for LLVM. > > It is built over llvm-c, and currently exposes enough APIs to build an > in-memory IR (and dump it!). It needs LLVM 2.3 latest and Python 2.5 > (2.4 should be sufficient, but I haven't tested). Tested only on > Linux/i386. > > Would love to hear

> From: OvermindDL1 <overminddl1 at gmail.com> > There could just as easily be language bindings between C++ and > Python, he chose the C bindings probably just because they were > easier, but they are most certainly not required. I know that is the > case in a few other scripting languages as well. He ( I :-) ) chose llvm-c based on the thread starting here:

Hi all, I'd like to announce the availability of Python bindings for LLVM. It is built over llvm-c, and currently exposes enough APIs to build an in-memory IR (and dump it!). It needs LLVM 2.3 latest and Python 2.5 (2.4 should be sufficient, but I haven't tested). Tested only on Linux/i386. Would love to hear your comments. [Needless to say, it's all work in progress, but mostly it

"Mahadevan R" <mdevan.foobar at gmail.com> writes: >> You could use llvm-gcc to convert the struct to an LLVM type. >> Otherwise, it wouldn't be too hard to convert the struct by >> hand as long as it doesn't have any exotic types in it. A >> VLA at the end (with element type T) is currently represented >> by placing a field of type T at the

Hello All, llvm-py 0.2 has been released. IR, execution engine, and (some) passes are now covered. There is also a much better website; code is now hosted on google code. Visit http://mdevan.nfshost.com/llvm-py/index.html for more details. Thanks & Regards, -Mahadevan.

Hi. Version 0.3 of llvm-py, Python bindings for LLVM, has been released. llvm-py now supports reading/writing of bitcode and LLVM assembly files, intrinsics and all the transformation passes. Also included are bug fixes and documentation/test updates. Home page: http://mdevan.nfshost.com/llvm-py/ Thanks & Regards, -Mahadevan.

Hi. Version 0.4 of llvm-py, Python bindings for LLVM, has been released. A few bug fixes, new APIs and code cleanup have gone in for this version. This will be the last release of llvm-py based on LLVM 2.3. Next version (0.5) will be based on LLVM 2.4 and will not be compatible with LLVM 2.3. I hope to release 0.5 very soon. Home page: http://mdevan.nfshost.com/llvm-py/ Thanks & Regards,

Hi (Gordon). There appears to be two wrapper functions for DerivedType::refineAbstractTypeTo() in llvm-c (Core.h, Core.cpp): void LLVMRefineAbstractType(LLVMTypeRef AbstractType, LLVMTypeRef ConcreteType){ DerivedType *Ty = unwrap<DerivedType>(AbstractType); Ty->refineAbstractTypeTo(unwrap(ConcreteType)); } void LLVMRefineType(LLVMTypeRef AbstractTy, LLVMTypeRef ConcreteTy) {