RFR: 8195685: AArch64: AArch64 cannot build with JDK-8174962
vladimir.kozlov at oracle.com
Mon Jan 22 03:24:00 UTC 2018
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:
> 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:
Rob, can Andrew push this fix (only aarch64 Hotspot changes) into jdk9u
Otherwise I can only suggest to talk to AdoptOpenJDK to respin aarch64
> I'm rather confused as regards jdk9u as there is no jdk9u-dev list to
> post to in order to request a backport. Red Hat wants to patch its
> downstream jdk9 repos but ideally this ought to go in upstream first.
> Also, the 9.0.4 Oracle release (built by AdoptOpenJDK?) is broken on
> AArhc64 so it really needs a respin after this patch has been included.
> Thanks in advance for any help or advice that can be offered.
> Andrew Dinn
> Senior Principal Software Engineer
> Red Hat UK Ltd
> Registered in England and Wales under Company Registration No. 03798903
> Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander
More information about the jdk-dev