harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Harmony Wiki] Update of "DRLVM Development Tasks" by Vladimir Beliaev
Date Fri, 15 Feb 2008 17:39:34 GMT
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 Vladimir Beliaev:

  '''''Task:''''' Move port_user_timezone() from DRLVM to classlib.
+ == JNI ==
+ === 4. Develop JNI Weak References ===
+ '''''Problem:''''' The Weak References implementation is required by [http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/functions.html#weak
Java Native Interface Specification]. Ok, it just needs to be implemented.
+ '''''Task:''''' Develop JNI Weak References.
+ == Launcher ==
+ === 5. Main Thread stack size control ===
+ '''''Problem:''''' ([https://issues.apache.org/jira/browse/HARMONY-4733 HARMONY-4733]) Java
Thread can be created with any stack size (limited by maximum), still the main Thread is provided
by the underlaying operation system, so its stack size can’t be changed, so this stack can
be simply overflowed – it is a problem. The solution is to keep the main system thread unused
and create the java main thread by VM means.
+ '''''Task:''''' Reimplement main thread processing in launcher.
  === <name> ===
  '''''Problem:''''' .
+ == The task fromn old list which required clarification ==
+ '''* Thread Manager'''
+ '''''Task:''''' From Weldon's April 2, 2007 dev@harmony posting titled, "[drlvm][threading]
a list of design/development issues that need coordination with the [general] M1 map", there
are 7 major areas that need to be focused on:  1) Thread Block Lifecycle, 2) storing thread
state in j.l.Thread object vs. native structs, 3) cleanup of internal Thread Manager mutex
design, 4) removing Thread Manager calls to APR, 5) analyze race conditions in lock reservation
(fix if required), 6) analyze the ThreadManager-JVMTI interface (fix if required), 7) Resolve
+ '''* Garbage Collection'''
+ '''''Task:''''' Implement SoftReference semantics: use heap usage information to make a
decision on resetting soft references. Currently soft reference act
+ exactly like weak references and are reset immediately after the target object became weakly
+ '''* MMTk Integration'''
+ ["MMTk Development Tasks"]

View raw message