harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chunrong Lai (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4477) [drlvm][gc_gen] Class Unloading support in DRLVM
Date Fri, 10 Aug 2007 02:21:42 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518891

Chunrong Lai commented on HARMONY-4477:

       Thanks for the review and discussion.
      (1)  I agree with you that we can always enumerate vtable->jlc as weak roots. Thanks
a lot. I did not distinguish the kind of the roots because I think duplicated marking for
a same object is not a issue.
             Yes. I slightly modified the original intended design because no backward pointer
to the vtable.
      (2)  XX:gc.ignore_weak_roots is actually a redundant option in current design. It is
only for the special case when the GC part of classunloading.options.diff.1 is finally committed
but the VM part is not commited.
             The option of XX:gc.force_major_collect=true is temporary just for the attached
test case which requires classes be unloaded in every collection. We do not need them if with
better test case.

> [drlvm][gc_gen] Class Unloading support in DRLVM
> ------------------------------------------------
>                 Key: HARMONY-4477
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4477
>             Project: Harmony
>          Issue Type: New Feature
>          Components: DRLVM
>         Environment: All
>            Reporter: Rana Dasgupta
>         Attachments: ClassUnloading.doc, classunloading.gcv5.classtracing.diff.1, classunloading.options.diff.1,
classunloading.prototype.diff.1, classunloading.weakroots.forgcv5.diff.1, Test_unloading_native_lib.zip
> This JIRA is intended as a placeholder for functional support for class unloading in
DRLVM. Remaining VM code mods, GC changes, tests, design will be submitted here.

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

View raw message