RFR: 8348203: [JVMCI] Make eager JVMCI initialization observable in the debugger
David Holmes
dholmes at openjdk.org
Thu Jan 23 06:05:51 UTC 2025
On Wed, 22 Jan 2025 14:46:36 GMT, Volker Simonis <simonis at openjdk.org> wrote:
> Yes, because that's the normal case. Usually, JVMCI gets initialized lazily,
Okay that alleviates my concern. I will leave it for JVMCI folk to approve.
> Is this a serious question? Because I'm hunting a bug in eager JVMCI initialization.
Yes a serious question but perhaps poorly framed. I was trying to gauge whether it makes sense to change the way the VM is doing this to address the debugging problem that you ran into i.e was this a general issue to be solved, or a one-of special case that should be handled by a local change instead.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/23219#issuecomment-2608933519
More information about the compiler-dev
mailing list