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 "Google Summer Of Code 2009 Projects Proposals" by IanRogers
Date Fri, 20 Mar 2009 11:22:46 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 IanRogers:

  || '''ASF Project''' || Apache Harmony http://harmony.apache.org ||
  || '''Keywords''' || Harmony, APR||
  || '''Description''' || To enable the Harmony class library to be easily ported to new platforms
a portability library exists. By replacing components in the portability library a VM may
integrate with the Harmony libraries. Alternatively a VM may use and build on the portability
library with Harmony. No current VM builds on top of just the portability library. The IBM
VMs use bespoke OS integration, DRLVM uses this and the Apache Portable Runtime (APR), Jikes
RVM uses the Harmony portability library and limited bespoke OS integration. The Apache Portable
Runtime differs from the Harmony portability library in that virtual memory functions are
exposed via mmap/munmap/mprotect rather than reserve/free/commit/decommit. The Harmony portability
library used to but no longer provides a portable signal handling mechanism. This project
will create a portability strategy for VMs using the Harmony class library either by using
the Harmony portability library, the Apache Portable Ru!
 ntime or potentially with no wrapper layer. One option is to recode the Harmony portability
library entirely using the APR, adding support for signal handling whilst also adding support
to APR for a different means of managing virtual memory. Another option is to put the portability
library functionality into APR. Alternatively no wrappers and adopting UNIX conventions may
best suppport portability. Ideally multiple open source Harmony VMs can be tested with this
portability layer such as DRLVM and Jikes RVM. This project will require consultation with
Harmony developers to form agreement and consensus on a portability strategy. Documenting
this strategy will also form part of the project.||
+ || '''Possible Mentors''' || Ian Rogers||
+ || '''Status''' || Unassigned ||

View raw message