Hi, in "Almost There - PyPy's ARM Backend" article is "The incomplete list of open topics":
-We are looking for a better way to translate PyPy for ARM, than the one describe above. I am not sure if there currently is hardware with enough memory to directly translate PyPy on an ARM based system, this would require between 1.5 or 2 Gig of memory. A fully QEMU based approach could also work, instead of Scratchbox2 that uses QEMU under the hood. -Test the JIT on different hardware. -Experiment with the JIT settings to find the optimal thresholds for ARM. -Continuous integration: We are looking for a way to run the PyPy test suite to make sure everything works as expected on ARM, here QEMU also might provide an alternative. -A long term plan would be to port the backend to ARMv5 ISA and improve the support for systems without a floating point unit. This would require to implement the ISA and create different code paths and improve the instruction selection depending on the target architecture. -Review of the generated machine code the JIT generates on ARM to see if the instruction selection makes sense for ARM. -Build a version that runs on Android. -Improve the tools, i.e. integrate with jitviewer. Which points is already done? Wiktor Mizdal _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
