[aarch64-port-dev ] RFR: 8195685: AArch64: AArch64 cannot build with JDK-8174962

Andrew Haley aph at redhat.com
Mon Jan 22 11:32:08 UTC 2018

On 22/01/18 03:24, Vladimir Kozlov wrote:
> On 1/21/18 8:25 AM, Andrew Dinn wrote:
>> On 20/01/18 12:14, Andrew Dinn wrote:
>>> On 19/01/18 19:01, jesper.wilhelmsson at oracle.com wrote:
>>>> Please note that we are now in RDP2 and there is a process to follow to
>>>> include the fix: http://openjdk.java.net/projects/jdk/10/rdp-2
>>>> In particular you need to add the label jdk10-fix-request to the JBS
>>>> issue to alert the release team about this bug. If not they don't know
>>>> that they have to wait for your fix to get done.
>>>> Please don't just add the label though, there is more to it.
>>> I have added the label and a Fix Request comment to the JIRA and linked
>>> the webrev to it.
>> Vladimir kindly responded to this with an approval on the JIRA. I am
>> still not sure where to go from here though:
>>    Can I/do I need to push the patch to the dev tree or the jdk10 tree?
> Yes, since it is arrch64 only changes, just push the fix into jdk10:
> http://hg.openjdk.java.net/jdk/jdk10/
>>    What do I need to do to get the patch into the jdk-updates jdk9u tree?
> As I understand 2018 CPU, 9.0.4 release was last one from Oracle:
> http://mail.openjdk.java.net/pipermail/jdk-updates-dev/2017-November/000024.html
> http://mail.openjdk.java.net/pipermail/jdk-updates-dev/2018-January/000031.html
> Rob, can Andrew push this fix (only aarch64 Hotspot changes) into jdk9u
> forest?:
> http://hg.openjdk.java.net/jdk-updates/jdk9u/hotspot

If Oracle doesn't want to do another release from jdk9u that's
entirely up to them, but Oracle broke the AArch64 port in JDK9, and we
need to fix it.  You can't go breaking ports and then disallowing
people from checking in the necessary fixes.

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the jdk-dev mailing list