This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Eclipse vs gij/libgcj, unit-at-a-time, -O2 and -O
- From: Tom Tromey <tromey at redhat dot com>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: java at gcc dot gnu dot org
- Date: 07 Nov 2003 13:38:13 -0700
- Subject: Re: Eclipse vs gij/libgcj, unit-at-a-time, -O2 and -O
- References: <1067897421.28101.121.camel@elsschot.wildebeest.org>
- Reply-to: tromey at redhat dot com
>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
Mark> The good news: I got Eclipse 2.1 and Eclipse 3.0 (M4, beta)
Mark> working with gij again. And it does run very nicely and fast,
Mark> even though it is completely interpreted.
Nice.
Mark> - The easy part is to define the following two properties for making it
Mark> at least startup and detect gcj as standard JRE (for JDT work):
Mark> java.vm.version=1.3
Does eclipse check this? That seems sort of bogus.
Mark> org.eclipse.core.runtime.ignoreLockFile=true
Why do we need this? I suspect this should lead to one or more
libgcj PRs :-)
Mark> I did disable the verifier in verify.cc. I don't know if that is
Mark> actually still necessary. Tom, is there a bug report for the issue you
Mark> had last time with Eclipse? If that cannot be easily fixed maybe we
Mark> should introduce a gij switch for disabling the verifier.
I believe the verifier in 3.4 should work fine. It still has one bug
pointed out by the mauve verifier tests, but as I recall this is a
trivial problem and results in the acceptance of invalid methods (so
it shouldn't erroneously reject anything).
Please try it. If you find a problem, let me know. I definitely want
this working for 3.4.
Tom