Thank you, Eric!
On Mon, May 6, 2024 at 7:21 PM wrote:
> On 5/6/24 09:26, Thomas Stüfe wrote:
> > Hi,
> >
> > is there a way to reliably prevent the jvm from being called with
> > -Xshare:dump during build?
> >
> > Often, when I tinker with metaspace or compressed klass pointers, CDS
> > gets
Hi Julian,
Yes, that confused me too. See here:
https://github.com/openjdk/jdk/blob/f308e107ce8b993641ee3d0a0d5d52bf5cd3b94e/make/GenerateLinkOptData.gmk#L76
Cheers, Thomas
On Tue, May 7, 2024 at 2:58 AM Julian Waters
wrote:
> Hi Thomas,
>
> --disable-jvm-feature-link-time-opt is for
Hi Thomas,
--disable-jvm-feature-link-time-opt is for disabling Link Time
Optimization when compiling the JVM itself, as in, requesting LTO from
the linker that is linking the JVM. It doesn't have anything to do
with what arguments the newly compiled JVM is called with and isn't
related to the
On 5/6/24 09:26, Thomas Stüfe wrote:
Hi,
is there a way to reliably prevent the jvm from being called with
-Xshare:dump during build?
Often, when I tinker with metaspace or compressed klass pointers, CDS
gets broken. During development, that is fine; it is a temporary state.
However, if
Hi,
is there a way to reliably prevent the jvm from being called with
-Xshare:dump during build?
Often, when I tinker with metaspace or compressed klass pointers, CDS gets
broken. During development, that is fine; it is a temporary state.
However, if -Xshare:dump is invoked, it may crash the
