This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
options for compiling large jars
- From: Per Bothner <per at bothner dot com>
- To: java at gcc dot gnu dot org
- Date: Fri, 15 Dec 2006 18:15:13 -0800
- Subject: options for compiling large jars
What are the recommended options for compiling large jars?
From what I can tell of Red Har's aot-compile script it
appears to compile a .jar file without optimization.
I can understand that, because it because when I compile
kawa.jar without optimization it is fairly quick (2m17s),
but when I compile with -O1 it takes forever.
Even using -fno-unit-at-a-time doesn't seem to help.
What I've done with Kawa before is compile one package
at a time, and that seems to work fairly well.
But I'm trying to figure out what changes are appropriate
in the new world, where we use ecj and gcj-dbtool.
(One change is it no longer makes sense to compile to
native from source if we also want .class files - instead
just compile *.class after generating those.)
--
--Per Bothner
per@bothner.com http://per.bothner.com/