hg: valhalla/valhalla: Merge

Remi Forax forax at univ-mlv.fr
Fri Feb 28 09:53:05 UTC 2020

Hi Jesper,
The other "recent" change is that the bootstrap jdk has to be jdk 14.

I build without Shenandoah, so the build is fine for me


----- Mail original -----
> De: "Jesper Steen Møller" <jesper at selskabet.org>
> À: "Tobias Hartmann" <tobias.hartmann at oracle.com>
> Cc: "valhalla-dev" <valhalla-dev at openjdk.java.net>
> Envoyé: Vendredi 28 Février 2020 09:58:50
> Objet: Re: hg: valhalla/valhalla: Merge

> Hi Tobias,
> I may have used "hg bisect" wrong, then. I'm still new to Mercurial.
> Thanks for the info.
> -Jesper
> On Fri, Feb 28, 2020 at 9:44 AM Tobias Hartmann <tobias.hartmann at oracle.com>
> wrote:
>> Hi Jesper,
>> On 28.02.20 09:39, Jesper Steen Møller wrote:
>> > I'm away from the machine at the moment, but I got a C++ build error
>> related to the Shenandoah code,
>> > just by trying a langtools tier1 test.
>> Okay, thanks for the details. Weird that you are only experiencing that
>> now, the Shenandoah build
>> error existed before the recent merge.
>> > I haven't done anything to explicitly disable Shenandoah, should I have
>> done that?
>> I've fixed all the Shenandoah related build problems, so it should build
>> fine now (if needed, you
>> can add --with-jvm-features=-shenandoahgc to your configure options to
>> disable the Shenandoah build).
>> Just make sure not to enable Shenandoah (at runtime) as it's currently not
>> supporting inline types.
>> Best regards,
>> Tobias

More information about the valhalla-dev mailing list