similar to: [LLVMdev] Status of Python bindings?

Hi, The person that developed the bindings is Jarno Seppänen , he sent me the code a few weeks ago. They were build with Boost.Python. The latest version was for LLVM 1.6 and the bindings seem to be unmaintained at the moment. From what I could tell they are very clean and probably easy to maintain/update to LLVM 1.7. From what I could tell from the email archive they were not far from

Hi, For the PyPy project ( http://codespeak.net/pypy ) I am working on the x64-64 support. I would like to use llc -march=ia64 to generate the assembly but that is not supported at the moment. As a workaround I let llc generate C code that gets compiled, but this unfortunately is not a good way to show the power of llvm. A understood this ia64 support will be worked on soon. First week of july

Hi, here's a brief update of the status of the python bindings. Recently I've updated them with the API changes in LLVM 1.6 and split the submodules (VMCore, ExecutionEngine, etc.) into separate builds, making the dynamic libraries smaller. I agree that the bindings should be in a CVS somewhere, and last year there was some discussion of putting them in the llvm tree. The python

You are right, the machine I am on is a AMD Opteron. I could probably generate working code for x86, but I am testing the implications of using 64 bits integers. The four weeks is not really important, it's just that it would be nice to have really fast code to showcase. Something related to this: to test the effect of 64 bits integers I replace all reference of int by long in my .ll file.

Hi there, The IA64 architecture, which had its 'official' name changed to the "Itanium Processor Architecture", *is* supported by llc. I am pretty sure you are talking about the x86-64 architecture, which has also had its share of unfortunate name changes and is also known as "AMD64", "EM64T" and all sorts of things in between. x86-64 is *not* currently

Hi, I would like to share my experimental LLVM API Python bindings with the LLVM enthusiasts. I have created Boost.Python wrappers largely for the VMCore interface and other selected interfaces (e.g. ExecutionEngine). The bindings provide direct runtime access to the LLVM bytecode and JIT execution features from Python. The bindings are complete enough so that one can e.g. run the Fibonacci

Jarno, This looks like it could be very valuable - thanks for making it available. Just out of curiosity, do you have any specific uses in mind for which you created these bindings? --Vikram http://www.cs.uiuc.edu/~vadve http://llvm.cs.uiuc.edu/ On Feb 23, 2005, at 5:21 PM, Jarno Seppänen wrote: > Hi, > > I would like to share my experimental LLVM API Python bindings with >

On Fri, 31 Oct 2003, Armin Rigo wrote: > Hello Chris, > > We have been investigating your project and the good documentation > and are very impressed. If we understood your goals correctly > this seems like a good match for our ongoing and active PyPy project, > a reimplementation of the Python language in Python. Cool. We are all big fans of Python here. :) > We'll

hello everyone, I few days ago I had some code (for the PyPy project) that llc - march=c converted to a switch statement and gcc compiled that nicely to a jumptable in the .s file. Now I try to reproduce when directly going from a .ll to a .s file. But I now see a long list of compare and jumps instead of the jumptable. Is there a transformation that does this if->switch(ing) or is

Hello LLVM-ers, The next sprint of PyPy will be held in Dallas, Texas, at the PyCon conference. Most of you know about the LLVM back-end of PyPy. So far, we use mostly the static compilation features of LLVM, but as we are progressing on the JIT side we are considering starting sometime soon working on just-in-time machine code generation backends. Clearly, LLVM might prove to be a good target

Hi Pertti, The boost Python are not (yet) part of LLVM so I suppose it would make most sense to try to makes fixes/changes so they would work for 1.7 and then try to get them into LLVM CVS. It would be good in such a case to ask the author of the bindings again if he would allow this, because basicaly I think he has to agree to the LLVM lincense. cheers, Eric On Apr 20, 2006, at 5:08

Hi, some discussion below. Reid wrote: > 3. Fix your Makefile to build a shared library properly. You have set > TOOLNAME which is for building an executable tool not a shared > library. You need to set LIBRARYNAME=..., not TOOLNAME=... I remember having failed to build a functioning Python extension module with LIBRARYNAME and SHARED_LIBRARY flags. Anyway, I cannot remember

Eric van Riet Paap wrote: > The boost Python are not (yet) part of LLVM so I suppose it would make > most sense to try to makes fixes/changes so they would work for 1.7 and > then try to get them into LLVM CVS. I tried compiling the bindings, and it seems that it would not be too much work to compile them for 1.7. I'm not familiar enough with LLVM to assess how complete the

On Fri, 23 Dec 2005, Eric van Riet Paap wrote: > I few days ago I had some code (for the PyPy project) that llc -march=c > converted to a switch statement and gcc compiled that nicely to a jumptable > in the .s file. Now I try to reproduce when directly going from a .ll to a .s > file. But I now see a long list of compare and jumps instead of the > jumptable. Is there a

> but I'd just like to point out that for python bindings at least, you > can quite easily manipulate the LLVM infrastructure via ctypes as a > shared object / dll -- no C required! Those of us interested in talking ctypes brings with it it's own troubles. To use it in any non-trivial way, one must write enough non-trivial wrapper code in Python. Performance is also affected

Hello LLVM, During this sprint we will also look at using LLVM JIT for our project. What exactly we will do in Tokyo very much depends on who will attend. So if you are interested please contact me beforehand so we can make sure everyone will have a fun and productive time. cheers, Eric van Riet Paap Tokyo PyPy Sprint: 23rd - 29th April 2006

Hello, I am developing an application which is Python based and uses LLVM. I use LLVM by generating textual bitcode files and feeding them to my plug-in. I wish LLVM had Python binding. I would love to see Python binding as one of the GSoC projects so someone from the community can pick it up. Cheers, Nadav

On Thu, 20 Apr 2006, [ISO-8859-1] Pertti Kellomäki wrote: > In my opinion, the most sensible thing to do with the bindings > right now would be to put them up on a CVS server somewhere. > Is there a chance of getting them at uiuc as a separate tree? > Another alternative would be to use SourceForge or something > similar. It would be straight-forward to make a new CVS module for

Hi, I've updated the Python LLVM bindings for LLVM 1.5 (attached). I also thought of setting up a CVS repository for this, but before I do that I thought I'd ask if you want to take the Python bindings to the main LLVM CVS? I noticed that the C language bindings would be maintained there. Changes in Python-LLVM: - Updated to match LLVM 1.5 API - Added Windows build support (created

Hi all, We're proud to announce... ========================================== PyPy 1.0: JIT compilers for free and more ========================================== Welcome to the PyPy 1.0 release - a milestone integrating the results of four years of research, engineering, management and sprinting efforts, concluding the 28 months phase of EU co-funding! Although still not mature enough