This is the mail archive of the
mailing list for the Java project.
Re: Patch for Review: Build all libjava .class files at once (UpdatedAgain)
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, <gnustuff at thisiscool dot com>, GCJ Patches <java-patches at gcc dot gnu dot org>
- Date: Tue, 16 Sep 2003 08:32:32 -0400 (EDT)
- Subject: Re: Patch for Review: Build all libjava .class files at once (UpdatedAgain)
On Tue, 16 Sep 2003, Andrew Haley wrote:
> If we're going to compile all the .calss files in a lump I'm tempted
> to try the same thing with compiling libgcj from source. We'd do lots
> of inlining and avoid many PLT indirections. I suppose compiling all
> of libgcj this way would probably be out of the question, but pieces
> with good locality might work well.
I agree. I had hoped libgcj could do this eventually. It'll solve part
of the linking problem, that of long command lines, and the overall linker
step may need a bit less memory. And it'll help avoid a particularly
onerous libtool bug in which libtool invokes ld -r directly, using the
wrong emulation on some targets (ppc64).
It'll also eliminate some duplicate Utf8's, shrinking libgcj.so slightly.
I was unsure of whether libtool would get in the way, i.e. whether
it will allow compiling multiple sources to one object. I tried it with a
recent libtool and it seems to work.