similar to: [LLVMdev] GC infrastructure checked in

Gordon Henriksen wrote: > On 2008-01-07, at 05:29, Jon Harrop wrote: > >> On Monday 07 January 2008 02:32:47 Gordon Henriksen wrote: >> >>> Everything described in GarbageCollection.html should now be live. >>> Phew! >>> >> This is wonderful news! Are there any example programs using these >> GCs? > > The division of labor is

On 2008-01-07, at 05:29, Jon Harrop wrote: > On Monday 07 January 2008 02:32:47 Gordon Henriksen wrote: > >> Everything described in GarbageCollection.html should now be live. >> Phew! >> > > This is wonderful news! Are there any example programs using these > GCs? The division of labor is such that the user program must provide the stack walker (in

On Jan 7, 2008, at 10:54, Carl Friedrich Bolz wrote: > Gordon Henriksen wrote: > >> 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. >> >> On his benchmarks, Armin saw an 8% speedup vs. a shadow stack. >> Their gcc backend still outperforms

pypy-0.7.0: first PyPy-generated Python Implementations ============================================================== What was once just an idea between a few people discussing on some nested mailing list thread and in a pub became reality ... the PyPy development team is happy to announce its first public release of a fully translatable self contained Python implementation. The 0.7 release

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

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

On Monday 07 January 2008 02:32:47 Gordon Henriksen wrote: > Everything described in GarbageCollection.html should now be live. Phew! > > The collectors could use a review, but they compile, have no impact > unless used, and tests would otherwise have had to be XFAILed waiting > on them. > > The ShadowStackCollector has one issue that may be of interest in that > it adds

Everything described in GarbageCollection.html should now be live. Phew! The collectors could use a review, but they compile, have no impact unless used, and tests would otherwise have had to be XFAILed waiting on them. The ShadowStackCollector has one issue that may be of interest in that it adds constant globals in a runOnFunction context. This is bad in theory, but actually 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 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

[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

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

Gordon Henriksen wrote: >> Hm, summary: >> >> pypy-llvm-backend with llvm's codegen >> < pypy-c-backend with GCC >> < pypy-llvm-backend using llvm's C backend and then GCC > > I wonder what the impact of using llvm-gcc instead of GCC is in this > final pipeline. If that actually works, you could indeed eliminate the > shadow stack

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