Build breaks if shenandoah is enabled
Aleksey Shipilev
shade at redhat.com
Mon Aug 19 06:40:22 UTC 2019
On 8/17/19 8:55 AM, Alan Bateman wrote:
> On 16/08/2019 23:41, Remi Forax wrote:
>> Hi all,
>> the current build breaks if shenandoah is enabled when building
>>
>> https://travis-ci.org/forax/java-next/jobs/572926707
>>
> I noticed this too but didn't get around to looking into it. You can workaround it temporarily by
> commenting out the STATIC_ASSERT in shenandoahUtils.cpp or run configure with
> --with-jvm-features=-shenandoahgc.
This is how you fix it properly:
http://cr.openjdk.java.net/~shade/loom/fix-shenandoah-nm-roots/webrev.01/
It includes the fix for JDK-8229865, that you would get via the next upstream pickup. The
STATIC_ASSERT would rightfully complain that new phase was added without corresponding Shenandoah
updates, and that is what the rest of the patch is fixing.
--
Thanks,
-Aleksey
More information about the loom-dev
mailing list