Shenandoah and aarch64

Andrew Haley aph at redhat.com
Fri Mar 20 12:19:49 UTC 2020


On 3/20/20 11:49 AM, Andrew Hughes wrote:
>
> On 20/03/2020 01:02, guoge (A) wrote:
>>>> Well, pretty much same as jdk11. We want to first backport LRB and
>>>> friends, which should clean up the shared code changes very
>>>> considerably. And after that, we shall comb through:
>>>>
>>>> https://builds.shipilev.net/patch-openjdk-shenandoah-jdk8-only-shared
>>>> /
>>>> hotspot/
>>>>
>>>> and sort out whatever is no longer needed.
>>>>
>>>> Right now it's mixed up with aarch64 changes, which is why I'd
>>>> probably push aarch64 to jdk8u first, which should be whatever is:
>>>>
>>>> http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/
>>>>
>>>> When this is done, we can take the complete patch and push it at once
>>>> to jdk8u.
>>>>
>>>> Do you agree?
>>>
>>> That sounds sensible. AArch64 is much less intrusive to the 8u code base than Shenandoah.
>>
>> We are interested in this issue. May I ask if there is any update on this please?
>
> I'm planning to get the AArch64 port into 8u for the 8u272 cycle (so
> integration sometime in June, release in October). I want to keep it out
> of the way of the JFR integration.

That sounds right. We have general consensus for AArch64 and JFR, so
we can stage things carefully :-) to suit our convenience.

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



More information about the jdk8u-dev mailing list