similar to: [LLVMdev] python & llvm

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

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

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

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

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

Not sure, but it seems the page contains a number of out-of-date entries: Pypy => pypy.org (link stale) plus: there is no llvm backend for pypy at the moment (although LLVM backends have been attempted a number of times, all seem to have failed) Unladen Swallow => not being developed since 2011 (http://qinsb.blogspot.com/2011/03/unladen-swallow-retrospective.html) TIA, Andreas The

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

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

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

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

Thanks for the report. The attached patch removes them from the page. OK? On 8 May 2013 11:34, Kostyrka (External user) Andreas <Andreas.Kostyrka at kapsch.net> wrote: > Not sure, but it seems the page contains a number of out-of-date entries: > > > > Pypy => pypy.org (link stale) plus: there is no llvm backend for pypy at the > moment (although LLVM backends have been

I updated the docs to show a pip/svn install like this: pip install svn+http://llvm.org/svn/llvm-project/lnt/trunk <svn+http://llvm.org/svn/llvm-project/lnt/trunk> > On Jul 18, 2017, at 11:24 AM, Kristof Beyls <kristof.beyls at arm.com> wrote: > > >> On 18 Jul 2017, at 20:21, Daniel Dunbar <daniel at zuster.org <mailto:daniel at zuster.org>> wrote:

I'd be fine pulling the pypi (sic) entry, shall I make it so? - Daniel On Tue, Jul 18, 2017 at 11:06 AM Chris Matthews <chris.matthews at apple.com> wrote: > Yep, we should pull that package down, or start to update it. > > The docs builds work for me. Is it possible that is not in your venv or > something like that? > > > On Jul 18, 2017, at 10:48 AM, Matthias

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

Hi Travis, ... > LLVM is still very relevant to Python because of projects like Numba --- but you > should know that PyPy is no longer using LLVM and Unladen Swallow has not been > worked on for several years. The future of LLVM and Python I think is very > bright --- especially for the scientific and data-analysis user-base. thanks for your interesting email. Do you understand

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.

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

Hello Duncan, > thanks for your interesting email. Do you understand why PyPy is no longer > using LLVM, and why Unladen Swallow died? Does LLVM need to be improved in > some way? The answers to all these questions are linked: LLVM is not fast enough (for a JIT). Of course this is not the whole story, but it is the LLVM-relevant part. Let's have a look at some random performance