Constant dynamic pushed to the hs repo
maurizio.cimadamore at oracle.com
Thu Feb 1 11:30:35 UTC 2018
We have some experimental changes in that vein in the amber repo - but
in general, support for condy in lambda requires updated ASM support,
and we'll get an updated ASM with condy support only _after_ JDK11 is
shipped. So, as a rule of thumb, features that rely on ASM (such as our
lambda metafactory) have to wait until the JDK ASM understands the new
On 01/02/18 02:48, Tagir Valeev wrote:
> Am I understand correctly that no javac changes were pushed (e.g.
> compiling lambdas using condy)?
> With best regards,
> Tagir Valeev.
> On Thu, Feb 1, 2018 at 9:39 AM, Brian Goetz <brian.goetz at oracle.com> wrote:
>> On 1/31/2018 5:43 PM, Paul Sandoz wrote:
>>> I just pushed the constant dynamic change sets to hs [*]. It took a little
>>> longer than I anticipated to work through some of the review process given
>>> the holiday break.
>>> We should now be able to follow up, in the hs repo until the merge in some
>>> cases, with dependent issues such as the changes to support AArch64, SPARC,
>>> AoT/Graal, additional tests, and some bug/performance fixes.
>>> [*] I’ll delay marking the JEP as integrated until a merge with the jdk
>>> master repo. After that we can then garbage collect the condy branch in the
>>> amber repo.
More information about the amber-dev