Return-Path: Delivered-To: apmail-harmony-commits-archive@www.apache.org Received: (qmail 32204 invoked from network); 10 Aug 2007 05:44:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Aug 2007 05:44:03 -0000 Received: (qmail 26636 invoked by uid 500); 10 Aug 2007 05:44:02 -0000 Delivered-To: apmail-harmony-commits-archive@harmony.apache.org Received: (qmail 26614 invoked by uid 500); 10 Aug 2007 05:44:02 -0000 Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list commits@harmony.apache.org Received: (qmail 26604 invoked by uid 99); 10 Aug 2007 05:44:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Aug 2007 22:44:02 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Aug 2007 05:44:03 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AADD171413F for ; Thu, 9 Aug 2007 22:43:42 -0700 (PDT) Message-ID: <15466819.1186724622668.JavaMail.jira@brutus> Date: Thu, 9 Aug 2007 22:43:42 -0700 (PDT) From: "Rana Dasgupta (JIRA)" To: commits@harmony.apache.org Subject: [jira] Commented: (HARMONY-4477) [drlvm][gc_gen] Class Unloading support in DRLVM In-Reply-To: <11147407.1184635444757.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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.