backport JDK-8130506 to 8 ?

Maurizio Cimadamore maurizio.cimadamore at oracle.com
Sat Jan 16 21:30:51 UTC 2016


I will leave the definitive answer to Srikanth, but from the looks of 
it, the patch seems trivial, so it doesn't seem crazy to backport it.

Maurizio

On 16/01/16 17:47, Remi Forax wrote:
> answsers inlined,
>
> ----- Mail original -----
>> De: "Jonathan Gibbons" <jonathan.gibbons at oracle.com>
>> À: compiler-dev at openjdk.java.net
>> Envoyé: Vendredi 15 Janvier 2016 21:52:36
>> Objet: Re: backport JDK-8130506 to 8 ?
>>
>> Rémi,
> Hi Jon,
>
>> There's maybe 3 parts to this:
>>
>> 1. Is it conceptually reasonable to backport the fix
> You can not do a methodHandle.invoke() inside a lambda in 8, so it's reasonable to backport the fix.
> Now, there are not a lot of people that uses java.lang.invoke API and the fact that the workaround is easy,
> replace the lambda by an inner class, backporting the fix may not worth it.
>
>> 2. Is it a relatively easy backport (i.e. does the fix for 9 apply reasonably
>> easily, or do we need a different fix, specific to 8)
> I believe the patch applies cleanly (minus the line number).
>
>> 3. Making it happen
>>
>> If folk can weigh in on 1 and 2, and the answer to both questions is "yes",
>> we can make 3 happen easily enough.
>>
>> -- Jon
> Rémi
>
>>
>>
>> On 01/15/2016 12:03 PM, Remi Forax wrote:
>>> Hi guys,
>>> the code I use to demonstrate how to create your own dynamically typed
>>> language on top of the JVM now triggers JDK-8130506 [1] :(
>>> i think the bug could have appear last year but last year none of my
>>> students was using IntelliJ IDEA, so the bug stay hidden.
>>>
>>> I wonder if the corresponding patch could be backported to 8, or maybe
>>> Attila and me are the only one to call MethodHandle.invoke inside a lambda
>>> ?
>>>
>>> cheers,
>>> Rémi
>>>
>>> [1] https://bugs.openjdk.java.net/browse/JDK-8130506
>>



More information about the compiler-dev mailing list