.. include:: crossreferences.asc

.. |title| replace:: Porting PyPy to an Embedded Device
.. |wp|    replace:: WP51
.. |start| replace:: M2
.. |p1|    replace:: X
.. |m1|    replace:: 3
.. |p2|    replace:: Y
.. |m2|    replace:: 3
.. |p3|    replace:: Y
.. |m3|    replace:: 3
.. |p4|    replace:: |e|
.. |m4|    replace:: |e|
.. |p5|    replace:: |e|
.. |m5|    replace:: |e|
.. |p6|    replace:: |e|
.. |m6|    replace:: |e|

.. include:: wp-toptable.asc

.. include:: wp-tablebegin.asc

**Objectives**

- Supporting a completely different platform
- Providing an efficient, high-level Language for 
  embedded Devices
- Proving the flexibility of the PyPy idea

.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc

**Description of work**

- Analyse the differences between the new architecture and
  PyPy's current. Deside whether to optimize for code size
  or applicatin speed.

- Develop the translation process, run-time and those optimisations
  that depend on low-level details.
  
- Implement a simulator for the embedded device.

- Implement interfaces to the needed external libraries.

- Combine different solutions for the different issues discussed in
  High-performance (WP42_, WP43_, WP44_). 
  Gather statistics with real-work Python applications.
  Compare the results. This is where the flexibility of the whole
  project is vital. Typically, very different trade-offs need to be
  made on different environments.

.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc

**Deliverables**

- DL??? Python running on the embedded device.
- DL??? Passing all applicable elements of the standard test suite.

.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc

**Milestones and Expected Result**

- M5

.. include:: wp-tableend.asc