I've been playing with some patches Christian tossed me around
JavaOne, to test out the new optimization logic that goes with the
LambdaForm implementation of invokedynamic.
So that others can play with it, I've uploaded an OS X build (Lion,
64-bit) here:
https://s3.amazonaws.com/openjdk/openjdk8
Hello all!
I've recently been informed that a new Ruby implementation is about to
be announced that puts JRuby's numeric perf to shame. Boo hoo.
It's not like I expected us to retain the numeric crown since we're
still allocating objects for every number in the system, but hopefully
we can get th
Good catch. Thanks for the report.
In hindsight, this irregularity is expressed in the JVM in
LinkResolver::check_method_accessability:
329 // Special case: arrays always override "clone". JVMS 2.15.
330 // If the resolved klass is an array class, and the declaring class
Tracking a bug in the backport, I've discovered that I forget to have a
special case for Object[].clone(),
the backport currently reports that the method is protected
(Object.clone is protected) thus not accessible.
The latest jdk8 binary also have some trouble with array.clone too.
public clas
On 10/16/2012 09:48 AM, John Rose wrote:
> On Oct 14, 2012, at 2:25 PM, Remi Forax wrote:
>
>> A value object is a true immutable object so the
>> JIT can constant fold field access or merge redundant access even if
>> there is method call between them but for that the JIT has to insert a
>> check
On Oct 14, 2012, at 2:25 PM, Remi Forax wrote:
> A value object is a true immutable object so the
> JIT can constant fold field access or merge redundant access even if
> there is method call between them but for that the JIT has to insert a
> check to know if the object is frozen (definitively
Changeset: 9193ecd53c82
Author:jrose
Date: 2012-10-16 00:18 -0700
URL: http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/9193ecd53c82
meth-lfi.patch: passes unit tests
! anno-stable.patch
+ meth-lfi.patch
! series
___
mlvm-dev mailing list
ml
