This is the mail archive of the java-patches@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: RFA: Changes to interpreter to avoid non-debugging slowdown

From: Keith Seitz <keiths at redhat dot com>
To: tromey at redhat dot com
Cc: Kyle Galloway <kgallowa at redhat dot com>, java-patches at gcc dot gnu dot org
Date: Tue, 01 Aug 2006 09:00:34 -0400
Subject: Re: RFA: Changes to interpreter to avoid non-debugging slowdown
References: <44CA8B0D.5030108@redhat.com> <17614.19859.287888.443036@localhost.localdomain> <44CF58ED.2080302@redhat.com> <17615.27921.726060.852247@localhost.localdomain>

Tom Tromey wrote:

So, I looked at JVMTI a little more.  It seems that we only need to
know the types of locals, is that correct?

Yeah, that's all that I can see/remember...

Are there other reasons we may want a special debug-only interpreter?
I thought Keith said there were, but I don't recall why exactly...

Yes, there is. While breakpointing won't interfere with the speed of the interpreter, I expect stepping support will be a much larger impact. I was planning on separating this into a debug interpreter to minimize the impact on the non-debug case.

Keith

Follow-Ups:
- Re: RFA: Changes to interpreter to avoid non-debugging slowdown
  - From: Tom Tromey

References:
- RFA: Changes to interpreter to avoid non-debugging slowdown
  - From: Kyle Galloway
- Re: RFA: Changes to interpreter to avoid non-debugging slowdown
  - From: Tom Tromey
- Re: RFA: Changes to interpreter to avoid non-debugging slowdown
  - From: Kyle Galloway
- Re: RFA: Changes to interpreter to avoid non-debugging slowdown
  - From: Tom Tromey

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