[aarch64-port-dev ] RFR: Bulk integration of Shenandoah 2018-05-15

[Aleksey Shipilev]

On 06/11/2018 06:06 AM, Andrew Hughes wrote:
> In working with this, I've run across changes like this:

These things are upstream jdk8u/jdk8u:

> changeset:   10408:908723b9f760
> user:        sangheki
> date:        Thu Feb 09 19:08:32 2017 -0800
> summary:     Cherry-pick JDK-8173013: JVMTI tagged object access needs
> G1 pre-barrier

https://bugs.openjdk.java.net/browse/JDK-8201583
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/767e8338f749

> changeset:   10409:388a0e0523c2
> user:        mdoerr
> date:        Tue Sep 06 13:01:27 2016 +0200
> summary:     Cherry-pick JDK-8165489: Missing G1 barrier in
> Unsafe_GetObjectVolatile

https://bugs.openjdk.java.net/browse/JDK-8202916
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/576949777967

> changeset:   10410:ea3ab1a51237
> user:        shade
> date:        Wed Feb 07 21:53:38 2018 +0000
> summary:     Cherry-pick JDK-8187577: JVM crash during gc doing
> concurrent marking

https://bugs.openjdk.java.net/browse/JDK-8187577
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/da2bb5e60234

> 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? We can do that. I
thought it would happen automatically with jdk8u pickup.

-Aleksey