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] Trivial Update of "DRLVM Development Tasks" by Vladimir Beliaev
Date Mon, 18 Feb 2008 15:03:07 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:
http://wiki.apache.org/harmony/DRLVM_Development_Tasks

The comment on the change is:
fixed spell errors

------------------------------------------------------------------------------
- This page contains a list of development tasks for the Harmony Virtial Machine (DRLVM) which
are not JIT or GC specific. If you pick a task please do not forget to let us know about your
choice in [http://incubator.apache.org/harmony/mailing.html the mailing list].
+ This page contains a list of development tasks for the Harmony Virtual Machine (DRLVM) which
are not JIT or GC specific. If you pick a task please do not forget to let us know about your
choice in [http://incubator.apache.org/harmony/mailing.html the mailing list].
  
  The list of tasks is being developed now, so it will be extended in nearest future. Also
the tasks will be reprioritized according to current needs of Apache Harmony project. There
is also a list of [http://wiki.apache.org/harmony/KnownNonBugIssuesAndLimitations Known Non
Bug Issues And Limitations] - most of issues are also a subject for resolution, so the development
task may be taken from that list.
  
@@ -8, +8 @@

  
  == Kernel Classes ==
  
- This section caontains a list of isolated development tasks, which do not require advanced
knowledge of VM and could be a nice start for newbies to get acquainted with the code. All
items are targeted for better code sharing.
+ This section contains a list of isolated development tasks, which do not require advanced
knowledge of VM and could be a nice start for newbies to get acquainted with the code. All
items are targeted for better code sharing.
  
  === 1. Improve/re-implement a Java5.0 generic signatures parser in DRLVM ===
  '''''Problem:''''' ([https://issues.apache.org/jira/browse/HARMONY-2052 HARMONY-2052]).
The current implementation is messy and half-baked, one needs to invent more shaped and modular
API to the module, develop a simple parser/lexer to avoid antlr dependency and move this functionality
to classlib (luni ?), so other VMs could reuse it for 1.5 support.
@@ -38, +38 @@

  == 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.
+ '''''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 underlying 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.
  
@@ -59, +59 @@

  == Finalization System ==
  
  === 7. Improve Finalization Work Balance Mechanism (FWBM) ===
- '''''Problem:''''' FWBM was changed with a move to new Garbage Collector (GCv5). This resulted
in FWBM becomes not well adjusted, the finalization system behaviour differes from RI one
which may be critical for stability and performance of resource critical applications. One
needs to evaluate FWBM in DRLVM and RI, identify issues (e.g. one may relate to dead lock
between finalizer thread and another thread using same monitor) and get them resolved.
+ '''''Problem:''''' FWBM was changed with a move to new Garbage Collector (GCv5). This resulted
in FWBM becomes not well adjusted, the finalization system behavior differs from RI one which
may be critical for stability and performance of resource critical applications. One needs
to evaluate FWBM in DRLVM and RI, identify issues (e.g. one may relate to dead lock between
finalizer thread and another thread using same monitor) and get them resolved.
  
  '''''Task:''''' Evaluate compatibility with RI and make required improvements.
  
@@ -87, +87 @@

  
  === 10. Implement VM specific utilities library ===
  
- '''''Problem:''''' Currently STL is used by set of DRLVM component, also it was practictied
to develop own simple utilities specific to particular components (aften produces the code
/ bugs duplication). One needs to identify the requirements for DRL-specific utilities and
approach the specific library for shared use (thus replace STL and inherent buggy utilities).
+ '''''Problem:''''' Currently STL is used by set of DRLVM component, also it was practiced
to develop own simple utilities specific to particular components (often produces the code
/ bugs duplication). One needs to identify the requirements for DRL-specific utilities and
approach the specific library for shared use (thus replace STL and inherent buggy utilities).
  
  '''''Task:''''' Design and implement the VM specific utilities library.
  
@@ -96, +96 @@

  === 11. Complete implementation of j.l.instrument ===
  '''''Problem:''''' The implementation of j.l.instrument contains a set of stabs instead
of code being directly connected to Virtual Machine internals. This may partially caused by
missed functionality in DRLVM. So one need to identify DRLVM requirements for j.l.instrument
support, develop the missed functionality to provide 100% support of j.l.instrument.
  
- '''''Task:''''' Develop unit test for j.l.instrumentation, identify the missed functionality
and get it developed.
+ '''''Task:''''' Develop unit test for j.l.instrument, identify the missed functionality
and get it developed.
  
  == The task from old list which required clarification ==
  

Mime
View raw message