[llvm-py] Future versions or roadmap

[Sebastian Muniz]

Hi,

I'm new to the group so first I want to say THANKS to everyone making
this project possible.

My question is simple... what are the plans for the project? Any
intention to release a new version soon?

I'm asking because I'm working on a project of my own and I'm using
LLVM-Py and I'd like to know of any upcoming feature.

Again... thanks a lot for the project.

~cheers, topo

[MD]

Hi Sebastian,

> My question is simple... what are the plans for the project? Any
> intention to release a new version soon?

Ideally, there should be a llvm-py release for every release of LLVM
itself.

Currently however, other projects keep me busy. If anyone is
interested in picking this up, do let me know.

> I'm asking because I'm working on a project of my own and I'm using
> LLVM-Py and I'd like to know of any upcoming feature.

The goal of llvm-py is just to provide Python bindings for the LLVM
libraries. It does not aim to provide anything more than that. Most of
it is covered already, but there are some more and others get added/
changed.

Regards,
-Mahadevan.

[Sebastian Muniz]

On 05/20/2010 12:41 AM, MD wrote:
> Hi Sebastian,
>
>> My question is simple... what are the plans for the project? Any
>> intention to release a new version soon?
>
> Ideally, there should be a llvm-py release for every release of LLVM
> itself.
>
> Currently however, other projects keep me busy. If anyone is
> interested in picking this up, do let me know.

I don't think I understand it enough (yet) to pick it up but I'm willing
to help with any test if you or someone else needs a beta-tester or
needs some help for the development.

>
>> I'm asking because I'm working on a project of my own and I'm using
>> LLVM-Py and I'd like to know of any upcoming feature.
>
> The goal of llvm-py is just to provide Python bindings for the LLVM
> libraries. It does not aim to provide anything more than that. Most of
> it is covered already, but there are some more and others get added/
> changed.

Well, I'm asking because of this last thing exactly. Some parts of LLVM
are not covered yet and I was wondering if someone is working on it. If
not, then it's ok... I just wanted to know any plans for the future.

Thanks for your quick response.

~cheers

[Baptiste Lepilleur]

2010/5/20 MD <mdevan...@gmail.com>

Hi Sebastian,

> My question is simple... what are the plans for the project? Any
> intention to release a new version soon?

Ideally, there should be a llvm-py release for every release of LLVM
itself.

Currently however, other projects keep me busy. If anyone is
interested in picking this up, do let me know.

For notes, the current version does not compile with LLVM 2.7 due to removal of ModuleProvider.h. I have not investigated this issue further.
 

> I'm asking because I'm working on a project of my own and I'm using
> LLVM-Py and I'd like to know of any upcoming feature.

The goal of llvm-py is just to provide Python bindings for the LLVM
libraries. It does not aim to provide anything more than that. Most of
it is covered already, but there are some more and others get added/
changed.

I think having a list of known missing features would be valuable.

There should probably be a list of update to TODO to synchronize with each LLVM version (e.g. new primitive types, passes...).
 

Regards,
-Mahadevan.

[Sebastian Muniz]

On 05/22/2010 07:29 AM, Baptiste Lepilleur wrote:
> 2010/5/20 MD <mdevan...@gmail.com>
>
>> Hi Sebastian,
>>
>>> My question is simple... what are the plans for the project? Any
>>> intention to release a new version soon?
>>
>> Ideally, there should be a llvm-py release for every release of LLVM
>> itself.
>>
>> Currently however, other projects keep me busy. If anyone is
>> interested in picking this up, do let me know.
>>
>
> For notes, the current version does not compile with LLVM 2.7 due to removal
> of ModuleProvider.h. I have not investigated this issue further.

It would be nice to have LLVM 2.7 supported :)

>
>
>> > I'm asking because I'm working on a project of my own and I'm using
>>> LLVM-Py and I'd like to know of any upcoming feature.
>>
>> The goal of llvm-py is just to provide Python bindings for the LLVM
>> libraries. It does not aim to provide anything more than that. Most of
>> it is covered already, but there are some more and others get added/
>> changed.
>>
>
> I think having a list of known missing features would be valuable.
>
> There should probably be a list of update to TODO to synchronize with each
> LLVM version (e.g. new primitive types, passes...).

I completely agree. Not only for people checking about the current state
of LLVM-PY before integrating it into their projects but also for people
already using it so they know what to expect in a future and may be
prepare certain parts of their project to accommodate upcoming LLVM-PY
features.

Another thing that would be nice to have are precompiled binaries
(specially for windows users who might have to setup lot's of thing to
get LLVM-PY up and running).
This might also encourage more users to start using LLVM-PY :)

~cheers, topo

[Jonathan Marshall]

Hi,

I'm also new to the group. Many thanks for this great project.

I took a quick look at 2.7. As well as ModuleProvider.h a number of
the passes seem to have been removed. I wasn't sure how to proceed. Do
you want to maintain 2.6 support? If so I'll need to figure out a way
to detect the version and do the right thing. For my personal copy I
just removed the offending code.

It still didn't work after that. I was getting some error when trying
to get a function pointer for my compiled code but I haven't had time
to debug.

I've also added a small number of features (for 2.6). The build also
needs to be fixed for Ubuntu 10.4 (libffi) and OS X (also libffi -
somebody else has submitted a patch for this, and I think I had to
make some changes for Snow Leopard because python on SL is 64 bit).

Let me know how you want to proceed with 2.6 vs 2.7. I should be able
to spend some time on preparing patches over the next 2 weeks but I
don't know if I'll have time to spare after that.

Thanks,

Jonathan.

On May 23, 1:22 am, Sebastian Muniz <sebastianmu...@gmail.com> wrote:
> On 05/22/2010 07:29 AM, Baptiste Lepilleur wrote:
>
>
>
>
>

> > 2010/5/20 MD <mdevan.foo...@gmail.com>

[Baptiste Lepilleur]

llvm-py for python 3.1 for windows is available precompiled in the download section of my toy project:
http://code.google.com/p/rpython/downloads/list

Baptiste.

2010/5/22 Sebastian Muniz <sebasti...@gmail.com>

On 05/22/2010 07:29 AM, Baptiste Lepilleur wrote:
> 2010/5/20 MD <mdevan...@gmail.com>
>

[...]

[Sebastian Muniz]

On 05/24/2010 06:04 AM, Baptiste Lepilleur wrote:
> llvm-py for python 3.1 for windows is available precompiled in the download
> section of my toy project:
> http://code.google.com/p/rpython/downloads/list

Yes, I saw it after I sent the email. It's cool but I think it should be
done by the LLVM-Py and not byt the users. Also I think that python 2.x
versions should be available because lots of people is still using it.

Thanks for letting us know about it and great project BTW :)

~cheers, topo