Re: Which file is the interpreter?

2009-09-22 Thread Christian Thalinger
James Ladd wrote:
 Hi All,
 
 I'm wading through the openJDK source and I'm wondering, which file or
 files are responsible for executing each bytecode ?
 
 ie: the loop that gets a bytecode, works out what is it and then dispatches
 it.

I think what you are searching for is templateTable_arch_model.cpp in
src/cpu/arch/vm/.

-- Christian
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev


Re: Which file is the interpreter?

2009-09-22 Thread Patrick Wright
James

You might take a look at Gary Benson's blog, as he's documented his
experience (as an outsider) working on a zero-assembly port of the
HotSpot interpreter (called Zero) and another compiler which targets
LLVM. His blog is at http://gbenson.net/; he's been documenting his
work for over a year, so it's helpful to page back through older
entries.


HTH
Patrick

On Tue, Sep 22, 2009 at 12:14 AM, James Ladd james_l...@hotmail.com wrote:
 Hi All,

 I'm wading through the openJDK source and I'm wondering, which file or
 files are responsible for executing each bytecode ?

 ie: the loop that gets a bytecode, works out what is it and then dispatches
 it.

 Rgs, James.

 
 Find out how here Use Messenger in your Hotmail inbox
 ___
 mlvm-dev mailing list
 mlvm-dev@openjdk.java.net
 http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev


___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev


hg: mlvm/mlvm/hotspot: indy.compiler: Fixed debug compilation, fixed bugs for bound

2009-09-22 Thread Christian . Thalinger
Changeset: 0db826e1d6d4
Author:twisti
Date:  2009-09-22 12:12 +0200
URL:   http://hg.openjdk.java.net/mlvm/mlvm/hotspot/rev/0db826e1d6d4

indy.compiler: Fixed debug compilation, fixed bugs for bound
MethodHandle adapters, fixed a problem with -Xcomp.

! indy.compiler.patch

___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev


backport

2009-09-22 Thread Raffaello Giulietti
I must confess that I never took a deep look at Rémi's backport. But
after having seen his report at the JVM Language Summit last Friday, I
must state that the results are quite impressing, given that it is a
library solution for indy rather than a JVM patch, as also noted by Neal
Gafter.

Pour ça, mes compliments à Rémi pour son travail et l'intuition qu'il a
eue de ne pas toucher le code original de la JVM mais de poursuivre une
solution alternative.

Kudos to Rémi.

Cheers
Raffaello

___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev


Re: backport

2009-09-22 Thread John Rose
Je conviens complètement.  Vive le backport!  -- John

On Sep 22, 2009, at 4:39 AM, Raffaello Giulietti wrote:

 I must confess that I never took a deep look at Rémi's backport. But
 after having seen his report at the JVM Language Summit last Friday, I
 must state that the results are quite impressing, given that it is a
 library solution for indy rather than a JVM patch, as also noted by  
 Neal
 Gafter.

 Pour ça, mes compliments à Rémi pour son travail et l'intuition  
 qu'il a
 eue de ne pas toucher le code original de la JVM mais de poursuivre  
 une
 solution alternative.

 Kudos to Rémi.

___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev


Re: Hotswap patch?

2009-09-22 Thread Thomas Wuerthinger
Patrick Wright wrote:
  Thomas--is any special flag required to enable this when launching the
  JVM if I build MLVM with your changeset in it? Also, I assume that if
  classes are redefined we will eventually run into the standard
  problems of PermGen limits on loaded classes?

No, there is no special flag required to enable my hotswap code. When 
you apply the changeset to jdk7-b51, you swap the current hotswapping 
implementation with my version.

Yes, with frequent use of hotswapping the problem of a limited PermGen 
arises. Especially as currently the old classes are still kept in the 
system. A fix for this might be to remove old classes from the system if 
none of their methods are active or reachable from active methods (and 
this is true for all of their subclasses).

- thomas
___
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev