Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 48453 invoked from network); 9 Dec 2007 11:36:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Dec 2007 11:36:37 -0000 Received: (qmail 29591 invoked by uid 500); 9 Dec 2007 11:36:24 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 29561 invoked by uid 500); 9 Dec 2007 11:36:24 -0000 Mailing-List: contact dev-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 dev@harmony.apache.org Received: (qmail 29552 invoked by uid 99); 9 Dec 2007 11:36:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Dec 2007 03:36:24 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xiaofeng.li@gmail.com designates 209.85.146.179 as permitted sender) Received: from [209.85.146.179] (HELO wa-out-1112.google.com) (209.85.146.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Dec 2007 11:36:03 +0000 Received: by wa-out-1112.google.com with SMTP id k22so2857680waf for ; Sun, 09 Dec 2007 03:36:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=O5WYFIjJumuFr715VgRyNOTZzRI63w3LWAJySR6O/Bw=; b=twoxuzEXeBS+mvLrWPaXUDOjoLMSQxXjlOAyn1II7No9jbtCZ6KvIfwL22RU/mii+Ps6GFgOfNwsJ/Zvzalmu8uHvKdiL0OtORyF/q5BOXaHSr5mpxGM7QgMxJAO7D3CcQdC9NHsGJqlaNHJF1KWFVUjGmLjIr4XqUihfIJa9ao= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CiDE0pUkvIqt+lebKjjoaFYDpfzeE6o8b2e8hHdJqN1E6eECeO0InHiKQazyLeJPybF3uX/3Lz575JtOncwdq9IQAQoZtfOrEzJG+pSQ2Gnchs5lR71kgM+sUxWDPCmFZl4fGOdknxxqC2KnRYzyPI5Y6qv90+BYYXbKTwa3VFg= Received: by 10.142.224.5 with SMTP id w5mr2632723wfg.1197200166525; Sun, 09 Dec 2007 03:36:06 -0800 (PST) Received: by 10.142.79.20 with HTTP; Sun, 9 Dec 2007 03:36:06 -0800 (PST) Message-ID: <9623c9a50712090336u621667f7r42c89119bd0ea6bc@mail.gmail.com> Date: Sun, 9 Dec 2007 19:36:06 +0800 From: "Xiao-Feng Li" To: dev@harmony.apache.org Subject: Re: Make GC_CC working In-Reply-To: <5ce835490712081811q5e787c84j24ef33c07fdecb9c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5ce835490712081811q5e787c84j24ef33c07fdecb9c@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org I'd like to have GC_CC in M4. If no objections in 24 hours, I will commit the patch. Thanks. -xiaofeng On Dec 9, 2007 10:11 AM, Ilya Berezhniuk wrote: > Hi All, > > Now we have GC_CC inoperable on most platforms - it works on > Windows/x86/release only. > > I've checked M3 build, GC_CC works fine (although hangs from time to time). > > > I suggest committing HARMONY-5247 and HARMONY-5262 patches to fix most > of current GC_CC problems. > > The problems are the following: > > 1) After r583223 threading commit GC_CC does not work in debug mode > because of multiple assertions. > > 2) After r587472 commit (symbols exporting policy) GC_CC was broken on > Linux because several symbols required by GC_CC were not added to EXP > files. > > 3) After r599482 commit (uncompressed references) GC_CC works > incorrectly on x86_64 because of changed object layout for 64bit > platforms. > > 4) GC_CC often hangs in shutdown. HARMONY-5136 has fixed the problem > for GC_GEN, but for GC_CC the problem still exists because of > different GC/Finalizer threads behavior. > > > HARMONY-5247 patch finally fixes the problem with shutdown deadlock on > ThreadGroup.lock monitor. > > > HARMONY-5262 patch fixes GC_CC problems 1) - 3). > > With both these patches all 'build test' tests are passed on > Windows/Linux x86 and on Linux/x86_64 in both debug and release modes. > > On 4-core Windows/x86_64 I've got 4 intermittent failures on debug > build (see details in HARMONY-5262), but these failures are not > reproducible on release build, and they also do not appear on 2-core > machine. > Looks like these failures are caused by some remaining threading > problems in GC_CC. > > Since HARMONY-5262 affects only GC_CC, all tests are passed with > GC_GEN on all 4 tested platforms. > > > I think it's valuable to make GC_CC working, if we are planning to > include it into M4 builds. > > > Thanks, > Ilya. > -- http://xiao-feng.blogspot.com