Shenandoah and aarch64
Andrew Haley
aph at redhat.com
Mon Jul 15 10:55:31 UTC 2019
On 7/14/19 12:21 PM, Roman Kennke wrote:
> 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.
Perfect. That could not be any better.
> 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.
That's OK, but ... that repo is cluttered with a lot of history.
Perhaps that doesn't matter, but it will be a confusing repo to work
on. Wouldn't something a bit cleaner be easier?
--
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 aarch32-port-dev
mailing list