This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Using gcj as a JIT Compiler
- From: Tom Tromey <tromey at redhat dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: Andrew Haley <aph at cambridge dot redhat dot com>, java at gcc dot gnu dot org
- Date: 09 Jan 2003 12:37:35 -0700
- Subject: Re: Using gcj as a JIT Compiler
- References: <Pine.LNX.4.44.0301031322190.19869-100000@ops2.one-point.com>
- Reply-to: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
Jeff> I've been using Ant as my testbed for -fno-assume-compiled. I'd
Jeff> like to simply do:
Jeff> gcj -c -fno-assume-compiled optional.jar
Jeff> and have it produce something. Currently optional.jar depends
Jeff> on a lot of third-party class libraries.
Some parts of Ant require things like com.sun.tools, don't they? For
those you'll need visible dummy definitions even with
-fno-assume-compiled. I ran into this problem in a few places (ant,
tomcat, junit).
Jeff> Ditto for Eclipse.
Recently I've been trying to compile Eclipse. Thanks to your
assume-compiled work I can get pretty far. It still doesn't start up,
but we're pretty close.
Maybe you could look at my latest assume-compiled patch and explain
the test I don't understand?
http://gcc.gnu.org/ml/java-patches/2003-q1/msg00054.html
If anyone is really interested in trying to make Eclipse start, I can
send my build script and other advice.
Tom