Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 14979 invoked from network); 9 Apr 2007 08:58:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Apr 2007 08:58:36 -0000 Received: (qmail 24833 invoked by uid 500); 9 Apr 2007 08:58:40 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 24799 invoked by uid 500); 9 Apr 2007 08:58:40 -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 24785 invoked by uid 99); 9 Apr 2007 08:58:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2007 01:58:40 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of zhanghuangzhu@gmail.com designates 209.85.134.190 as permitted sender) Received: from [209.85.134.190] (HELO mu-out-0910.google.com) (209.85.134.190) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Apr 2007 01:58:33 -0700 Received: by mu-out-0910.google.com with SMTP id w1so2108013mue for ; Mon, 09 Apr 2007 01:58:11 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=b09kh09prLV7CpJV5jYWvF7tjtDa7IDNoyjn0Y0+EVjUp0K6TAN0a3PXxjNv8NKce/In4KgpGbfG9sP6bW6/61df42TnGzpQI91oJcNOE1aPxeIR6oTm1jIUtyqspVBob8tbqJKLbf4O89HYa7Q0IqmRzBCrSpjF+3iujaA9Mlw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=MZIBxd5nYWzYUwSKxukxhaS52d5z2waHIideC/tOZDyVkeD+mH62bZ5vCPM9RImq571+Y3rBzWyq5yD57y2H7TcOV71vkFJlH/nmLdvZ3R1/DOsFPB+5w00XFVu7Q50xn80IxwWiJ0f0R+wSVENMzEfEfMIugccWkHi6NtBzDAw= Received: by 10.82.108.9 with SMTP id g9mr7329123buc.1176109091736; Mon, 09 Apr 2007 01:58:11 -0700 (PDT) Received: by 10.82.116.2 with HTTP; Mon, 9 Apr 2007 01:58:11 -0700 (PDT) Message-ID: <4d0b24970704090158qc5d21cs7e85fc001b4aa272@mail.gmail.com> Date: Mon, 9 Apr 2007 16:58:11 +0800 From: "Andrew Zhang" To: dev@harmony.apache.org Subject: Re: [contribution] Contribution of charset encoders/decoders for NIO_CHAR module In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_35803_8400603.1176109091639" References: X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_35803_8400603.1176109091639 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 4/9/07, Vladimir Strigun wrote: > > Hi all! > > I'm happy to announce one more contribution to harmony on behalf of > Intel. Provided implementation of charset encoders/decoders is > intended to replace the ICU-based charsets encoding/decoding > operations. The code was developed in clean-room environment inside > Intel and I'd like you to play with it and include to current Harmony > tree. > > The package could be found there: > HARMONY-3593 > > The algorithms for charsets encoding/decoding differs from that of > ICU, all charsets are generated from current Harmony or any other > implementation of Java and could be properly integrated into current > nio_char module. The archive contains source files for 6 charsets: > GB18030, US-ASCII, ISO-8859-1, UTF-8, UTF-16, UTF-16BE, UTF-16LE; > implementation of CharsetProvider; generator for other Charsets and > native part. I've tested the package with more that 90 charsets, and > all benchmarks and tests passed with new bundle. Additionally I have > significant boost for Dacapo.antlr and Dacapo.xalan benchmarks with > current Harmony tree on DRLVM and IBM VM. On DRLVM I have 2.5x boost > for antlr and ~5-8x for xalan. > > The main advantages of the package are the following: > - Code for every charset is generated by CharsetGenerator, thus, if > some modification would be necessary we need just correct generator > and re-generate all sources. > - We use 2 different encoders and decoders for java and direct > buffers. Since most applications use java heap buffers, unlike > existing implementation it doesn't produce lots of native calls to > perform encoding/decoding operations on the java buffers those > significantly improving performance. This is the main reason why we > have such a significant boost for Dacapo. > - Charset tables for encoding/decoding are stored in appropriate > classes. > > Since the package contains implementation for 6 charsets only, > documentations how to generate and build additional charsets you could > find in README file from contributed package. > > Please do not hesitate to contact me for more details. Hi Vladimir, Does it include the source code of hycharset.dll? Thanks, > Vladimir. > -- Best regards, Andrew Zhang ------=_Part_35803_8400603.1176109091639--