[aarch64-port-dev ] RFR: Bulk integration of Shenandoah 2018-05-15
Andrew Hughes
gnu.andrew at redhat.com
Wed Jun 13 15:02:43 UTC 2018
On 11 June 2018 at 08:22, Aleksey Shipilev <shade at redhat.com> wrote:
snip...
>
>> We shouldn't be backporting upstream changes into just Shenandoah. These should go first to
>> jdk8u/jdk8u, and then, if we need them before they make an upstream 8u release, they should go to
>> aarch64/jdk8u.
> So your concern here is that we need to get those into aarch64/jdk8u first?
My concern is that we're creating needless differences between
aarch64/jdk8u and aarch64/jdk8u-shenandoah.
> We can do that. I
> thought it would happen automatically with jdk8u pickup.
It will when we pull in whatever 8u version they are destined for.
8187577 is scheduled for the next
CPU (8u181), the other two for the feature update 8u192 in October.
Clearly though, you want them for Shenandoah earlier than that. In
this case, add them to aarch64/jdk8u
and then merge that into the Shenandoah tree, rather than applying
directly to Shenandoah. That way,
all three trees (the two aarch64 project ones and the Shenandoah
project one) have these fixes.
>
> -Aleksey
>
>
Thanks,
--
Andrew :)
Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Web Site: http://fuseyism.com
Twitter: https://twitter.com/gnu_andrew_java
PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222
More information about the aarch64-port-dev
mailing list