[pypy-dev] Fwd: Anyone interested in a MIPS port...

Vishal vsapre80 at gmail.com
Mon Oct 17 08:21:47 CEST 2011

Forwarding it again to pypy-dev. Sorry missed the first time.


---------- Forwarded message ----------
From: Vishal <vsapre80 at gmail.com>
Date: Sun, Oct 16, 2011 at 10:51 PM
Subject: Re: [pypy-dev] Anyone interested in a MIPS port...
To: Armin Rigo <arigo at tunes.org>

Thanks Armin.

Appreicate your  email a lot. I had sort of lost track of this message. My
final target is actually a 32 bit microcontroller from Microchip, the very
famous PIC32 family. RAM is a big issue there...atleast I dont know what is
the exact way of expanding ram on that architecture.
MIPS though is available from many other companies, and has been the
embedded workhorse of the last decade.

Will be happy to help to someone who would take the lead in this effort.

The python-on-a-chip project is more what microcontroller guys should look

Take care,

On Wed, Aug 24, 2011 at 6:44 PM, Armin Rigo <arigo at tunes.org> wrote:

> Hi Vishal,
> On Sat, Aug 20, 2011 at 3:53 PM, Vishal <vsapre80 at gmail.com> wrote:
> > a) Does it make sense to have a MIPS port of the PyPy JIT.
> Yes, it definitely makes sense.  I assume that the MIPS machines you
> consider as final targets have *some* amount of RAM, like, say,
> minimum 32MB or 64MB.  PyPy would have issues running on smaller
> machines, let alone with the JIT.
> > b) How much hardware dependent is a JIT port?
> You need to write pypy/jit/backend/mips/, similar to the other
> existing JIT backends: x86 (the only one nightly tested), ARM or
> PowerPC.  This is the only hardware-dependent part (not e.g. the JIT
> front-end): it receives a list of operations (generic operations
> represented as nice objects, like "integer addition" and "read this
> field from that pointer") and must turn it into machine code.
> Sven and David are currently working on the PowerPC backend in the
> branch "ppc-jit-backend", if you want to follow; it is still at an
> early stage, which means that the amount of code so far should be
> reasonable.
> Sorry to answer this late, it seems that nobody is very much
> interested in contributing...  All I can promise myself is to give you
> some help, as I do right now with Sven. :-)
> A bientôt,
> Armin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20111017/1d5128b6/attachment-0001.html>

More information about the pypy-dev mailing list