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: Bryce McKinlay <bryce at mckinlay dot net dot nz>
- Cc: Jeff Sturm <jsturm at one-point dot com>, Mark Wielaard <mark at klomp dot org>, <java at gcc dot gnu dot org>
- Date: 03 Dec 2003 12:45:47 -0700
- Subject: Re: Eclipse vs gij/libgcj, unit-at-a-time, -O2 and -O
- References: <Pine.LNX.4.44.0311292320270.31967-100000@ops2.one-point.com><CAC3AF58-252B-11D8-A689-003065F97F7C@mckinlay.net.nz>
- Reply-to: tromey at redhat dot com
>>>>> "Bryce" == Bryce McKinlay <bryce@mckinlay.net.nz> writes:
Tom> I think a better approach is to register the ffi closure stubs
Tom> instead. Those are unique per method and they'll let us get rid of
Tom> the linear search of interpreted stack frames.
Jeff> I'm not really sure what you mean by this. It is my understanding that
Jeff> the closures are invisible to a stack trace.
Bryce> Right, I looked into this but came to the same conclusion: ffi stubs
Bryce> have no stack frame, so they can't be seen in a stack trace.
Ah, sorry. I thought AG had had this working at one point. I didn't
actually look into it myself.
Tom