This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Eclipse vs gij/libgcj, unit-at-a-time, -O2 and -O

From: Bryce McKinlay <bryce at mckinlay dot net dot nz>
To: Jeff Sturm <jsturm at one-point dot com>
Cc: Tom Tromey <tromey at redhat dot com>,Mark Wielaard <mark at klomp dot org>, <java at gcc dot gnu dot org>
Date: Wed, 3 Dec 2003 13:58:22 +1300
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>

On Nov 30, 2003, at 5:25 PM, Jeff Sturm wrote:

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'm not really sure what you mean by this.  It is my understanding that
the closures are invisible to a stack trace.

Right, I looked into this but came to the same conclusion: ffi stubs have no stack frame, so they can't be seen in a stack trace.

Regards

Bryce.

Follow-Ups:
- Re: Eclipse vs gij/libgcj, unit-at-a-time, -O2 and -O
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]