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

[Andrew Haley]

On 05/17/2018 01:28 PM, Roman Kennke wrote:
> Am 15.05.2018 um 16:50 schrieb Roman Kennke:
>> This integrates latest Shenandoah changes from shenandoah/jdk8u
>> repository. It includes all Shenandoah changes since Oct 2017. It's all
>> backports from sh/jdk -> sh/jdk10 -> sh/jdk9 -> sh/jdk8u or jdk8u
>> specific bugfixes. It's all been reviewed, baked and
>> thoroughly tested upstream.
>>
>> The integration brings lots of major and minor improvements, bugfixes
>> and tests.
>>
>> The list of changesets to be pushed is this:
>> http://cr.openjdk.java.net/~rkennke/jdk8u-shenandoah-integration-2018-05-15/jdk8u-shenandoah-integration-2018-05-15.txt
>>
>> The complete webrev is:
>> http://cr.openjdk.java.net/~rkennke/jdk8u-shenandoah-integration-2018-05-15/webrev.00/
>>
>> It builds release+fastdebug, and passes all hotspot_gc_shenandoah tests.
>>
>> I'll tag the forest with:
>>
>> aarch64-shenandoah-jdk8u172-b11--shenandoah-merge-2018-05-15
>>
> 
> I also want to include this:
> http://hg.openjdk.java.net/shenandoah/jdk8u/hotspot/rev/84f19550a9d5
> 
> to fix build issues on windows. It applies cleanly.
> 
> Can I please get a review?

That looks reasonable.

Is there a well-defined process for handling changes as the GC
interface progresses in upstream trunk?  Is it a matter of
back-porting the GC interface to JDK 8, or do you still do things the
"old" way?

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671