Anyone interested in a MIPS port...
Hello, I would like to collect volunteers for a MIPS port of PyPy JIT. MIPS is used across the embedded scene universally and a PyPy support for MIPS would be wonderful. So I have 2 questions (may seem like very nuby like...pardon me for that): a) Does it make sense to have a MIPS port of the PyPy JIT. b) How much hardware dependent is a JIT port? Thanks and best regards, Vishal Sapre
Hi Vishal, On Sat, Aug 20, 2011 at 3:53 PM, Vishal <vsapre80@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.
Hello everyone, On 24 August 2011 15:14, Armin Rigo <arigo@tunes.org> wrote:
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. :-)
I'm also interested in contributing to a MIPS port of the JIT backend. Is there any tip for cross-compiling PyPy that I should know about before beginning ? Thanks, -- Nicolas « kalenz » Hureau
On Sun, Oct 16, 2011 at 11:00 AM, Nicolas Hureau <nicolas.hureau@gmail.com> wrote:
Hello everyone,
On 24 August 2011 15:14, Armin Rigo <arigo@tunes.org> wrote:
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. :-)
I'm also interested in contributing to a MIPS port of the JIT backend.
Is there any tip for cross-compiling PyPy that I should know about before beginning ?
Thanks,
Cross compiling pypy is a bit hairy because PyPy (at translation time) queries underlaying Python enviroment for some details. You might be able to get rid of that, but it's a bit of work. We're here to help though. And no, there are no cross-compiler tools I'm aware of. Cheers, fijal
On 16.10.2011, at 20:03, Maciej Fijalkowski <fijall@gmail.com> wrote:
On Sun, Oct 16, 2011 at 11:00 AM, Nicolas Hureau <nicolas.hureau@gmail.com> wrote:
Hello everyone,
On 24 August 2011 15:14, Armin Rigo <arigo@tunes.org> wrote:
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. :-)
I'm also interested in contributing to a MIPS port of the JIT backend.
Is there any tip for cross-compiling PyPy that I should know about before beginning ?
Thanks,
Cross compiling pypy is a bit hairy because PyPy (at translation time) queries underlaying Python enviroment for some details. You might be able to get rid of that, but it's a bit of work. We're here to help though. And no, there are no cross-compiler tools I'm aware of.
Cheers, fijal _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
On Sun, Oct 16, 2011 at 20:03, Maciej Fijalkowski <fijall@gmail.com> wrote:
On Sun, Oct 16, 2011 at 11:00 AM, Nicolas Hureau <nicolas.hureau@gmail.com> wrote:
Hello everyone,
On 24 August 2011 15:14, Armin Rigo <arigo@tunes.org> wrote:
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. :-)
I'm also interested in contributing to a MIPS port of the JIT backend.
Is there any tip for cross-compiling PyPy that I should know about before beginning ?
Thanks,
Cross compiling pypy is a bit hairy because PyPy (at translation time) queries underlaying Python enviroment for some details. You might be able to get rid of that, but it's a bit of work. We're here to help though. And no, there are no cross-compiler tools I'm aware of.
Cheers, fijal
Hi, I have been using the scratchbox2 http://freedesktop.org/wiki/Software/sbox2toolchain to cross-translate PyPy for ARM targeting the Ubuntu ARM port. There is bit of documentation about using it in the ARM branch at https://bitbucket.org/pypy/pypy/src/arm-backend-2/pypy/doc/arm.rst Maybe the information there is helpful for MIPS. Greetings, David
participants (5)
-
Armin Rigo -
David Schneider -
Maciej Fijalkowski -
Nicolas Hureau -
Vishal