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: Jeff Sturm <jsturm at one-point dot com>
- Cc: Mark Wielaard <mark at klomp dot org>, java at gcc dot gnu dot org
- Date: 29 Nov 2003 14:01:44 -0700
- Subject: Re: Eclipse vs gij/libgcj, unit-at-a-time, -O2 and -O
- References: <Pine.LNX.4.44.0311291507390.19585-100000@ops2.one-point.com>
- Reply-to: tromey at redhat dot com
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
Jeff> So the eclipse code calls the single-argument Class.forName(),
Jeff> which walks the stack frame to find a loader and fails,
Jeff> presumably because _Jv_StartOfInterpreter and
Jeff> _Jv_EndOfInterpreter no longer surround the
Jeff> _Jv_InterpMethod::run method in generated code.
This is a bogus approach and we knew it, we just were hoping to get
away with it.
I think a better approach is to register the ffi closure stubs
instead. Those are unique per method and they'll let us get rid of
the linear search of interpreted stack frames.
I know Bryce was doing some work in this area recently, but I don't
know the status of it.
Tom