harmony-commits mailing list archives

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

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

Rana Dasgupta commented on HARMONY-4477:
----------------------------------------

Thanks Chunrong.
1) Also seems that there is a potential to avoid a lot of data structure duplication here
by using pre/post processing GC<->VM hooks that Xiaofeng discussed on the list.
2) About force_major_collect...I agree. To use this limited test to check the CU machinery
it is OK to turn the option on, I think. But in our design, we commit to do CU at every major
collection only...not at every collection.

This is ready for commit IMHO. We can add the stuff in 3997 ( lazy exception handling impact
) later after this core functionality goes thru some testing.

> [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.


Mime
View raw message