From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26427 invoked by alias); 21 Apr 2010 22:11:05 -0000 Received: (qmail 26355 invoked by uid 22791); 21 Apr 2010 22:11:04 -0000 X-SWARE-Spam-Status: No, hits=-0.0 required=5.0 tests=BAYES_20,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_GC X-Spam-Check-By: sourceware.org Received: from mail-pw0-f47.google.com (HELO mail-pw0-f47.google.com) (209.85.160.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Apr 2010 22:10:56 +0000 Received: by pwj5 with SMTP id 5so4932051pwj.20 for ; Wed, 21 Apr 2010 15:10:54 -0700 (PDT) Received: by 10.115.101.31 with SMTP id d31mr6183920wam.151.1271887854038; Wed, 21 Apr 2010 15:10:54 -0700 (PDT) Received: from jdpc-core1.ecovate.com (204-133-153-190.dia.static.qwest.net [204.133.153.190]) by mx.google.com with ESMTPS id b6sm1204522wam.9.2010.04.21.15.10.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 21 Apr 2010 15:10:53 -0700 (PDT) Date: Wed, 21 Apr 2010 22:11:00 -0000 From: Joel Dice To: Monty Hall cc: java@gcc.gnu.org Subject: Re: gcj for j2me In-Reply-To: <4BCF731A.8080007@rastar.merseine.nu> Message-ID: References: <4BCF731A.8080007@rastar.merseine.nu> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2010-04/txt/msg00006.txt.bz2 On Wed, 21 Apr 2010, Monty Hall wrote: > Anybody had success compiling j2me code w/ gcj? I've noticed that javac > doesn't do a stellar job doing compile time optimization and that very > limited mobile device jvm's pretty much don't do optimization. Would be > handy to do compile time optimizations for mobile devices. Any pointers > appreciated. ProGuard (http://proguard.sourceforge.net) does static bytecode optimization, including some pretty impressive whole-program optimizations like devirtualization and inlining across interface calls. That might be the easiest solution if your target device already has a VM.