Shenandoah and aarch64

[Roman Kennke]

>>> 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? 

In what, specifically, are you interested? AArch64 port in jdk8, or
Shenandoah in jdk8 or both?

The Shenandoah backport is currently stalled in jdk11, and it's not
clear yet if and how this is going to be resolved:

https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2020-January/002399.html


We will not backport it to 8u before it's in 11u.

Until this happens, you can use the backport repositories in the
Shenandoah projects:

Shenandoah/jdk8:
http://hg.openjdk.java.net/shenandoah/jdk8/

Shenandoah/jdk11:
http://hg.openjdk.java.net/shenandoah/jdk11/

They are following upstream jdk-updates closely, and include a
well-maintained Shenandoah backport. The shenandoah/jdk8 repository also
includes the aarch64 port.

I hope that helps.

Roman