I've seen two bugs like this before, and they both had the same cause:
assuming the second argument is at index 1 (for static methods, 2 for
instance methods). If a method takes a double and something else (e.g.
an int), then accessing the double works fine, but accessing the int
gives a verif
John Rose a écrit :
> On May 12, 2009, at 4:25 PM, Rémi Forax wrote:
>
>
>>> And it works like a charm :)
>>>
>>>
>> untile the next bug ...
>> The following code crash.
>> It doesn't crash if there is only one invokedynamic.
>>
>
> Perhaps it's a problem with converting the floating
On May 12, 2009, at 4:25 PM, Rémi Forax wrote:
>> And it works like a charm :)
>>
> untile the next bug ...
> The following code crash.
> It doesn't crash if there is only one invokedynamic.
Perhaps it's a problem with converting the floating-point argument? I
don't think my regression tests g
Rémi Forax a écrit :
> John Rose a écrit :
>
>> I hope b59 smells better. I just pushed the changes I've chosen for
>> b59 to the patch repo.
>>
>> I am working on other changes too, but I am in point-fix mode, as JDK7
>> M3 settles down for JavaOne.
>>
>> My goal at the moment is to find w
