search for: rigo

Displaying 17 results from an estimated 17 matches for "rigo".

Did you mean: rig
2008 Jan 07
2
[LLVMdev] GC infrastructure checked in
...the GC), so complete GC programs are nontrivial. This is somewhat similar to the state of exception handling in LLVM. It would be an excellent project to provide reference implementations of these facilities. 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 the LLVM backend, though—and llvm-gcc outperforms that further still. So perhaps those llvm-gcc GC extensions could be put to go...
2008 Jan 07
0
[LLVMdev] GC infrastructure checked in
...ms are > nontrivial. This is somewhat similar to the state of exception > handling in LLVM. It would be an excellent project to provide > reference implementations of these facilities. > > 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 the LLVM backend, though—and llvm-gcc > outperforms that further still. The second part of this is not corr...
2005 Jun 22
2
[LLVMdev] Re: Re: variable sized structs in LLVM
Hi Reid, On Tue, Jun 21, 2005 at 11:15:22PM -0700, Reid Spencer wrote: > If you believe that variable sized structs are a feature that is missing > in LLVM, then that's another discussion. However, LLVM needs to remain > "low level" and it is unlikely such a feature would gain much traction > since a combination of existing features can accomplish the same thing. The
2008 Jan 07
0
[LLVMdev] GC infrastructure checked in
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
2008 Jan 07
0
[LLVMdev] GC infrastructure checked in
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
2003 Oct 31
5
[LLVMdev] Re: LLVM and PyPy
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 Pyth...
2008 Jan 07
2
[LLVMdev] GC infrastructure checked 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 the LLVM backend, though—and >> llvm-gcc outperforms that further still. > > The s...
2008 Jan 07
3
[LLVMdev] GC infrastructure checked in
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
2003 Oct 31
0
[LLVMdev] Re: LLVM and PyPy
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, >...
2005 Aug 29
0
[LLVMdev] PyPy release 0.7.0 announcement
...give feedback and raise questions. contact points: http://codespeak.net/pypy/dist/pypy/doc/contact.html contributor list: http://codespeak.net/pypy/dist/pypy/doc/contributor.html have fun, the pypy team, of which here is a partial snapshot of mainly involved persons: Armin Rigo, Samuele Pedroni, Holger Krekel, Christian Tismer, Carl Friedrich Bolz, Michael Hudson, Eric van Riet Paap, Richard Emslie, Anders Chrigstroem, Anders Lehmann, Ludovic Aubry, Adrien Di Mascio, Niklaus Haldimann, Jacob Hallen, Bea During, Laura Creighton, and many con...
2005 May 20
0
[LLVMdev] PyPy 0.6 released
...that far without the coding and feedback support from numerous people. Please feel free to give feedback and raise questions. contact points: http://codespeak.net/pypy/index.cgi?contact contributor list: http://codespeak.net/pypy/index.cgi?doc/contributor.html have fun, Armin Rigo, Samuele Pedroni, Holger Krekel, Christian Tismer, Carl Friedrich Bolz PyPy development and activities happen as an open source project and with the support of a consortium funded by a two year EU IST research grant. Here is a list of partners of the EU project:...
2005 Nov 03
0
[LLVMdev] PyPy 0.8 release announcement
...munity effort from the start and it would not have got that far without the coding and feedback support from numerous people. Please feel free to give feedback and raise questions. contact points: http://codespeak.net/pypy/dist/pypy/doc/ contact.html have fun, the pypy team, (Armin Rigo, Samuele Pedroni, Holger Krekel, Christian Tismer, Carl Friedrich Bolz, Michael Hudson, and many others: http://codespeak.net/pypy/dist/pypy/doc/ contributor.html) PyPy development and activities happen as an open source project and with the support of a consortium partially funded...
2007 Mar 27
0
[LLVMdev] PyPy 1.0: JIT compilers for free and more
...e goals and form of the next stage of development - now more than ever depending on your feedback and contributions - and we hope you appreciate PyPy 1.0 as an interesting basis for greater things to come, as much as we do ourselves! have fun, the PyPy release team, Samuele Pedroni, Armin Rigo, Holger Krekel, Michael Hudson, Carl Friedrich Bolz, Antonio Cuni, Anders Chrigstroem, Guido Wesdorp Maciej Fijalkowski, Alexandre Fayolle and many others: http://codespeak.net/pypy/dist/pypy/doc/contributor.html What is PyPy? ================================ Technically, PyPy i...
2003 Nov 04
0
[LLVMdev] Re: LLVM and PyPy
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
2003 Oct 31
0
[LLVMdev] Re: LLVM and PyPy
Hello Chris, On Fri, Oct 31, 2003 at 10:58:45AM -0600, Chris Lattner wrote: > These are definitely features that we plan to add, but just haven't gotten > to yet. In particular, Alkis is working on a Java front-end, which will > require similar features. In the beginning, we will probably just use a > conservative collector, eventually adding support for precise GC. Great!
2007 Jun 22
0
[LLVMdev] Vilnius/Post EuroPython PyPy Sprint 12-14th of July
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
2006 Feb 10
2
[LLVMdev] PyPy sprint announcement: PyCon 2006, Texas, Feb 27st - March 2nd
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