Please take with a grain of salt, as I'm not a pypy dev. In general: yes it's a great idea! arm64 definitely fits the bill in terms of hardware and arm64 devices could really use pypy. I have some reservations in terms how far this can be pushed in a single summer, but hey, it's good to be ambitious!
In terms of development and testing: Given enough host ram, you could try to translate pypy under arm64 qemu directly. It's going to be slow, by about factor of 10, but set up is much easier. Other thoughts: ARM memory [synchronisation] model is different than x86, I bet the difference is present in 64-bit version too. Given that most popular arm hardware is now multicore, the issue cannot be avoided. You'd need a core dev to provide guidance here. d. On 16 March 2015 at 18:42, Manuel Jacob <m...@manueljacob.de> wrote: > Hi, > > I decided that this year is a good time to apply for GSoC. Because I never > worked on anything JIT-related, this could be a chance to get started with > it. There was some discussion about possible improvements for the ARM > backend. Also, some newer ARM processors support a 64-bit execution mode > called AArch64. I think it makes sense to implement a JIT backend for > AArch64 sooner or later. There are just a few affordable AArch64 > development boards available at the moment, but I was able to cross-compile > a non-jitted version of PyPy and run it in QEMU. > > Do you think that implementing an AArch64 JIT backend is a good GSoC > project? If not, can you think of other JIT-related projects that fit > better in the scope of GSoC? > > -Manuel > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
