On Jan 7, 2011, at 2:48 AM, Christian Thalinger wrote:
> Wait a second... I doubt this is a false negative in VerifyMethodHandles.
> The MethodHandleWalker can't find a raw retype conversion function and that's
> why it crashes. Maybe it is a false negative but then we are missing some
> con
On Jan 7, 2011, at 11:08 AM, Christian Thalinger wrote:
> On Jan 7, 2011, at 10:43 AM, John Rose wrote:
>> On Jan 7, 2011, at 1:30 AM, Christian Thalinger wrote:
>>
>>> Can you look at the false negative? I will fix the checking logic.
>>
>> Sure. Please throw me a recipe (concise if possible)
On Jan 6, 2011, at 3:16 AM, John Rose wrote:
> On Jan 5, 2011, at 4:56 AM, Christian Thalinger wrote:
>
>> I looked into this bug and the cause is that the method handles are not
>> verified. Running with a debug build or using
>> -XX:+UnlockDiagnosticVMOptions -XX:+VerifyMethodHandles with a p
On Jan 7, 2011, at 10:43 AM, John Rose wrote:
> On Jan 7, 2011, at 1:30 AM, Christian Thalinger wrote:
>
>> Can you look at the false negative? I will fix the checking logic.
>
> Sure. Please throw me a recipe (concise if possible) for reproducing the
> error. -- John
I have no small testcas
The home package for JSR 292 is likely to change soon from "java.dyn" to
"java.lang.mh" (or a similar name).
The name "java.dyn" was chosen several years ago, long before method handles or
Project Lambda. Our JDK7 architecture and future plans have changed enough to
warrant moving the content
Changeset: 2d609a524177
Author:jrose
Date: 2011-01-04 23:29 -0800
URL: http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/2d609a524177
meth, indy: additional EG-driven fixes
! meth.patch
! meth.test.patch
Changeset: dd25ec3f4b74
Author:jrose
Date: 2011-01-07 01:45 -0800
URL:
On Jan 7, 2011, at 1:30 AM, Christian Thalinger wrote:
> Can you look at the false negative? I will fix the checking logic.
Sure. Please throw me a recipe (concise if possible) for reproducing the
error. -- John
___
mlvm-dev mailing list
mlvm-dev@o
On Jan 6, 2011, at 3:16 AM, John Rose wrote:
> On Jan 5, 2011, at 4:56 AM, Christian Thalinger wrote:
>
>> I looked into this bug and the cause is that the method handles are not
>> verified. Running with a debug build or using
>> -XX:+UnlockDiagnosticVMOptions -XX:+VerifyMethodHandles with a p