hg: valhalla/valhalla: Merge
Jesper Steen Møller
jesper at selskabet.org
Fri Feb 28 08:58:50 UTC 2020
I may have used "hg bisect" wrong, then. I'm still new to Mercurial.
Thanks for the info.
On Fri, Feb 28, 2020 at 9:44 AM Tobias Hartmann <tobias.hartmann at oracle.com>
> 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,
More information about the valhalla-dev