Forwarding it again to pypy-dev. Sorry missed the first time.<div><br></div><div>Regards,</div><div>Vishal<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Vishal</b> <span dir="ltr"><<a href="mailto:vsapre80@gmail.com">vsapre80@gmail.com</a>></span><br>
Date: Sun, Oct 16, 2011 at 10:51 PM<br>Subject: Re: [pypy-dev] Anyone interested in a MIPS port...<br>To: Armin Rigo <<a href="mailto:arigo@tunes.org">arigo@tunes.org</a>><br><br><br>Thanks Armin.<div><br></div><div>
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.</div>
<div>MIPS though is available from many other companies, and has been the embedded workhorse of the last decade.</div><div><br></div><div>Will be happy to help to someone who would take the lead in this effort.</div><div>
<br></div><div>The python-on-a-chip project is more what microcontroller guys should look at.</div><div><br></div><div>Take care,</div><div>Vishal</div><div><div><div></div><div class="h5"><br><div class="gmail_quote">On Wed, Aug 24, 2011 at 6:44 PM, Armin Rigo <span dir="ltr"><<a href="mailto:arigo@tunes.org" target="_blank">arigo@tunes.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Vishal,<br>
<div><br>
On Sat, Aug 20, 2011 at 3:53 PM, Vishal <<a href="mailto:vsapre80@gmail.com" target="_blank">vsapre80@gmail.com</a>> wrote:<br>
</div><div>> a) Does it make sense to have a MIPS port of the PyPy JIT.<br>
<br>
</div>Yes, it definitely makes sense. I assume that the MIPS machines you<br>
consider as final targets have *some* amount of RAM, like, say,<br>
minimum 32MB or 64MB. PyPy would have issues running on smaller<br>
machines, let alone with the JIT.<br>
<div><br>
> b) How much hardware dependent is a JIT port?<br>
<br>
</div>You need to write pypy/jit/backend/mips/, similar to the other<br>
existing JIT backends: x86 (the only one nightly tested), ARM or<br>
PowerPC. This is the only hardware-dependent part (not e.g. the JIT<br>
front-end): it receives a list of operations (generic operations<br>
represented as nice objects, like "integer addition" and "read this<br>
field from that pointer") and must turn it into machine code.<br>
<br>
Sven and David are currently working on the PowerPC backend in the<br>
branch "ppc-jit-backend", if you want to follow; it is still at an<br>
early stage, which means that the amount of code so far should be<br>
reasonable.<br>
<br>
Sorry to answer this late, it seems that nobody is very much<br>
interested in contributing... All I can promise myself is to give you<br>
some help, as I do right now with Sven. :-)<br>
<br>
<br>
A bientôt,<br>
<font color="#888888"><br>
Armin.</font></blockquote></div></div></div></div></div><br>
</div>