.. include:: crossreferences.asc

.. |title| replace:: Specific Analysis and Redesign
.. |wp|    replace:: WP32
.. |start| replace:: WP31_
.. |p1|    replace:: X
.. |m1|    replace:: 4
.. |p2|    replace:: Y
.. |m2|    replace:: 4
.. |p3|    replace:: |e|
.. |m3|    replace:: |e|
.. |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**

- Putting interpreter (WP21_, WP22_) and translator (WP31_) together.
- Enhancing the PyPy Design.

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

**Description of work**

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

**Part a): Specific Analysis and Redesign**

- Investigate the particular problems that the
  global translation of PyPy is going to raise.
- Enhance and redesign parts of PyPy as needed
  to give best support to the translation of RPython.
- Re-iterate this until we agree to have reached
  an optimum solution.
  
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc

**Deliverables**

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

**Milestones and Expected Result**

- M2 with WP33_

.. include:: wp-tableend.asc