[jira] Closed: (HARMONY-4494) [drlvm][classloader] VM modification for class unloading

["Xiao-Feng Li (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HARMONY-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xiao-Feng Li closed HARMONY-4494.
---------------------------------

    Resolution: Fixed

HARMONY-4477 was committed, so this is no longer needed.

> [drlvm][classloader] VM modification for class unloading
> --------------------------------------------------------
>
>                 Key: HARMONY-4494
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4494
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>         Environment: win32
>            Reporter: Chunrong Lai
>         Attachments: classunloading.vm.diff
>
>
>  The patch is not intended for commit but only for review purpose.
>  I did them in VM side (to SVN HEAD) to test the GCv5's CU work where the references from native heap to java heap (m_loader, m_class_handle, vtable->jIC) are enumerated as weak roots at certain time. Then GCv5 will trace the strong roots and update the weak roots. 
>  Currently the intergated version can pass smoke test, specjbb and several other benchmarks. It also successfully unloaded the classloaders when running the test case in "Test_unloading_native_lib.zip".
>  There are two more issues:
>     (1) Attached is just an unconditional-unloading approach. Extra interfaces are needed to achieve selective unloading.
>     (2) Some code refinements need to be done if running in 64bits environment since GC and VM use different code conventions to compress the references. If VM use the uncompressed "ManagedObject* vtable->jIC" as in the attachment we only need enhance GC in future.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.