jdk9/hs is CLOSED

Christian Thalinger christian.thalinger at oracle.com
Thu May 12 19:39:13 UTC 2016


> On May 12, 2016, at 5:17 AM, Jesper Wilhelmsson <jesper.wilhelmsson at oracle.com> wrote:
> 
> Den 12/5/16 kl. 16:52, skrev Andrew Haley:
>> On 05/12/2016 03:12 PM, Jesper Wilhelmsson wrote:
>>> Den 12/5/16 kl. 16:10, skrev Andrew Haley:
>>>> On 05/12/2016 03:06 PM, Christian Tornqvist wrote:
>>>>> FC means that no RFE/Features can be pushed without approval from the JDK 9
>>>>> Release Team. The updated schedule was published to the OpenJDK community in
>>>>> December last year by Mark Reinhold.
>>>> 
>>>> You're not helping very much.  Or rather, you're restating what I've
>>>> heard already but I don't know what that means.  Is finishing off the
>>>> compact string intrinsics for AArch64 a RFE/Feature or not?  I don't
>>>> know.  As far as I'm concerned it's a work in progress, which started
>>>> some time ago.
>>> 
>>> Do you have a JBS ID for this work?
>> 
>> I thought so, but I can't see it.  I've been tending to create ad-hoc
>> bugs for each part of the work.  But the need for it is implied by JEP
>> 254: Compact Strings.  So you're perhaps telling me that if I had
>> known that it was necessary to get this done, I should have created
>> one?
> 
> I was mainly looking for something to read to try to figure out if this is an enhancement or a bug. From your description it could be either.

It’s an enhancement.  As far as I know Compact Strings works fine without compiler intrinsics; it’s just slow.

The more interesting question is if Oracle’s rules should also apply to non-shared code changes to ports that Oracle does not maintain.

> 
> JEP 254 is clearly a new feature and as such should be integrated before FC. It was integrated in November 2015. Is it a bug that the parts you are fixing now doesn't work..? I don't know.
> 
> You will need a JBS ID to push your changes anyway so I suggest you create a bug for this (and make it a "Bug"). If no-one complains and it passes triage as a bug I guess it is a bug and then you can push it when the repo opens again.
> 
> /Jesper



More information about the hotspot-dev mailing list