similar to: [LLVMdev] PyPy release 0.7.0 announcement

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

Hello LLVM-ers, Below you will a description of our new PyPy release, a project which (among many other things)generates one of the largest .ll files in existance. :-) This .ll gets compiled with the LLVM toolchain into a standalone executable of the Python language. I hope you find this interesting! cheers, Eric van Riet Paap ==============================================================

Hi LLVM-dev! I have been working for a few months on an experimental LLVM backend for the PyPy project and I thought you might be interested in the fact that we just did our first public release, which includes it (see release announcement below). Regards Carl Friedrich The PyPy 0.6 release -------------------- *The PyPy Development Team is happy to announce the first public release

[The first part of the announcement did not make it into the previous mail] Hello LLVM-ers, Most of you know of the LLVM backend in PyPy. We would like to use LLVM JIT for the next phase of PyPy. If any of you would like to help us, please come to Gothenburg next december. We have not put an LLVM track on the todo-list below mainly because no one will be there dedicated to LLVM. If

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

Hi all, For those of you following PyPy, our next sprint has "porting to LLVM 2.0" as one of its topics. ======================================================== Vilnius/Post EuroPython PyPy Sprint 12-14th of July ======================================================== The PyPy team is sprinting at EuroPython again and we invite you to participate in our 3 day long sprint at the

Hi LLVM-dev! As you know, I'm involved with the PyPy Python compiler effort and have been wroking on the LLVM backend. The LLVM backend will be one of the topics of the upcoming PyPy sprint (see link below), which will take place in Heidelberg, Germany. See sprint announcement below or on http://codespeak.net/pypy/index.cgi?extradoc/sprintinfo/Heidelberg-sprint.html Since we only started

Hello LLVM-ers, Most of you know of the LLVM backend in PyPy. We would like to use LLVM JIT for the next phase of PyPy. If any of you would like to help us, please come to Gothenburg next december. We have not put an LLVM track on the todo-list below mainly because noone will be there dedicated to LLVM. If however someone would like to participate we will make sure some of the PyPy

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 Chris, [Chris Lattner Fri, Oct 31, 2003 at 10:58:45AM -0600] > On Fri, 31 Oct 2003, Armin Rigo & Holger Krekel 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,

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

Hi LLVM-dev! As you know, I'm involved with the PyPy Python compiler effort and have been writing the LLVM backend (actually, I have written two LLVM backends by now :-) . The LLVM backend will be one of the topics of the upcoming PyPy sprint (see link below), which will take place in Gothenburg, Sweden. Since I only started using LLVm half a year ago my experience with it is somewhat

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 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

Hello, Everyone > That said, the PyPy group has llvmgcroot support on a branch; you > could ask Armin Rigo <arigo at tunes dot org> for details about > accessing it. FYI: some status report can be seen here: http://codespeak.net/pipermail/pypy-dev/2008q1/004441.html -- WBR, Anton Korobeynikov

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.

Hello Chris, On Sun, Nov 02, 2003 at 10:56:34AM -0600, Chris Lattner wrote: > > driving LLVM from LLVM code is closer to our needs. Is there a specific > > interface to do that? > > Sure, what exactly do you mean by driving LLVM code from LLVM? Writing LLVM code that contains calls to the LLVM framework's compilation routines. Sorry if this is a newbie question, but are

Hi Armin, > 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, How are you using the static compilation features? Are you able to do this via API calls or generating code that will be processed by tools? Thanks, Marcel

Hi, working on the LNT documentation I am wondering about a few things: - LNT documentation recommends to do `easy_install lnt==0.4.2dev` (in the install box on the left side of the title page). The last available version of LNT on pypy is version 0.4.0 from 2012. Are there plans to keep this up to date or should we better remove the entry and not mention pypy packages anymore? - Building the