Shenandoah and aarch64

[Andrew John Hughes]

On 14/07/2019 12:21, Roman Kennke wrote:
>> On 12/07/2019 11:08, Andrey Petushkov wrote:
>>> Azul fully supports this idea and would like to propose integration of aarch32 port as well, please
>>>
>>> Regards,
>>> Andrey
>>>
>>>> On 11 Jul 2019, at 19:31, Hohensee, Paul <hohensee at amazon.com> wrote:
>>>>
>>>> We (Amazon) are interested in pushing both Shenandoah and the aarch64 port to jdk8u and would be willing to do much/most of the work. I believe that both currently reside in http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/ (correct me if not), so to me the easiest approach would be to take both from there. I’d move Shenandoah first, since it presumably has hooks in platform dependent code which we’d have to work around if we did the aarch64 port first.
>>>>
>>>> Thoughts?
>>>>
>>>> Thanks,
>>>>
>>>> Paul
>>>
>>
>> I agree, it would be good to finally see both ports in the main upstream
>> repository. Shenandoah as well, though that should go to 11 first.
>>
>> The work should use a staging repository, as with JFR, so as to minimise
>> disruption to the work on 8u releases.
> 
> For the Shenandoah part, would shenandoah/jdk11 work as staging repo? It
> seems to be the obvious choice because we already have it, and it is
> supposed to only contain the actual difference between upstream jdk11u
> and Shenandoah.
> 
> For jdk8, I am not quite sure. We do have shenandoah/jdk8. I believe it
> probably would make sense to separate the aarch64 integration into 8u
> from Shenandoah and not make Aarch64 wait for Shenandoah. In this case,
> I think shenandoah/jdk8 would be good as staging for Shenandoah into
> jdk8u too.
> 
> Roman
> 

When I refer to a staging repository, I mean something that could be
pulled into the mainline jdk8u/jdk8u-dev i.e. something that has a
series of changesets that have valid bug IDs and pass jcheck.

I don't know how clean sh/jdk11 is now, but aarch64/jdk8u-shenandoah
certainly isn't in that state.

I would suggest starting with getting Shenandoah into 11u and aarch64
into 8u (the two efforts can run in parallel). Once Shenandoah has
soaked into 11u, it can be backported to 8u, by which time it should
have aarch64.

It'd be nice to get aarch64 into 7u too, but that's probably wanting too
much :-)
-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222
https://keybase.io/gnu_andrew