harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David P Grove <gro...@us.ibm.com>
Subject Re: [arch] VM/Classlibrary Interface (take 2)
Date Mon, 11 Jul 2005 13:54:29 GMT
> > 3. Don't worry about inlining Java code: assume the VM can do 'easy'
> >    inlining like invoking static methods.
> How does that aspect matter to the VM/classlib interface?

        It matters in that when defining the VM/classlib interface you 
should assume that adding a level of "easy" to inline wrapper functions 
will have zero performance impact.  Eg, Object.clone isn't directly 
declared to be a native method, it simply delegates to VMObject.clone, 
which may or may not be a native method depending on the VM 
implementation.  Trust that the JIT will inline away the trivial wrapper 
method (java.lang.Object.clone) so that delagating the real work to a 
method of VMObject won't cost you anything.


View raw message