You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by Apache Wiki <wi...@apache.org> on 2009/03/24 01:58:08 UTC

[Harmony Wiki] Update of "Google Summer Of Code 2009 Projects Proposals" by XiaoFeng Li

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Harmony Wiki" for change notification.

The following page has been changed by XiaoFeng Li:
http://wiki.apache.org/harmony/Google_Summer_Of_Code_2009_Projects_Proposals

------------------------------------------------------------------------------
  || '''Possible Mentors''' || Mark Hindess (committer)||
  || '''Status''' || Unassigned ||
  
+ || '''Subject ID''' || ''harmony-JIT-1'' ||
+ || '''Title''' || ''' Modularize Harmony JIT by separating JET as a standalone JIT compiler ''' ||
+ || '''ASF Project''' || Apache Harmony http://harmony.apache.org ||
+ || '''Keywords''' || Harmony, JVM, JIT, modularity ||
+ || '''Description''' || So far the JIT component (called Jitrino) of Harmony has virtually two JIT implementations: JET and OPT. Jitrino.JET is a fast but non-optimizing JIT, and Jitrino.OPT is an optimizing JIT. The code base of JET and OPT shares lots of code hence they are mixed in one module. This is undesirable for situations where people need only JET, for fast compilation, for small footprint. This project proposes to create a standalone JET-based JIT module for Harmony. It does not require to remove JET from Jitrino, but to create a new JIT module with JET. This project is also a very good exercise to examine the JIT modularity design, the interface between JIT and other components, the interaction between multiple co-existing JIT modules. ||
+ || '''Possible Mentors''' || Xiao-Feng Li (committer)||
+ || '''Status''' || Unassigned ||
+