This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: options for compiling large jars
- From: Tom Tromey <tromey at redhat dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: java at gcc dot gnu dot org
- Date: 16 Dec 2006 09:16:50 -0700
- Subject: Re: options for compiling large jars
- References: <458356B1.2000006@bothner.com>
- Reply-to: tromey at redhat dot com
>>>>> "Per" == Per Bothner <per@bothner.com> writes:
Per> What are the recommended options for compiling large jars?
Per> From what I can tell of Red Har's aot-compile script it
Per> appears to compile a .jar file without optimization.
The script we use when making RPMs (I forget if it is aot-compile or
aot-compile-rpm, I think the name changed or something) will split up
large jars and compile them piecemeal. We had to do this not only
because large jars make gcj use too much memory, but also due to GOT
overflows on PPC.
I think the script we use also omits non-.class files when compiling.
If you're deploying using the class map .db then you need the jars
around anyhow, and resources compiled into a .so will just waste space
and not be used.
Tom