RFR: 8308151: [JVMCI] capture JVMCI exceptions in hs-err

Doug Simon dnsimon at openjdk.org
Tue May 16 21:26:52 UTC 2023

On Tue, 16 May 2023 16:43:01 GMT, Tom Rodriguez <never at openjdk.org> wrote:

>> src/hotspot/share/jvmci/jvmciRuntime.cpp line 2047:
>>> 2045:                                                                      (jlong) compile_state, compile_state->task()->compile_id());
>>> 2046: #ifdef ASSERT
>>> 2047:   if (JVMCIENV->has_pending_exception() && JVMCICompileMethodExceptionIsFatal) {
>> It's a shame to introduce a VM flag (i.e., `JVMCICompileMethodExceptionIsFatal`) for a test case but I don't know of any other way to do this. As far as I know, system properties cannot be accessed here. Maybe using an environment variable is better than a VM flag?
> Why can't you use a JVMCI property for this?  You get a chance to see them when copying them to Graal.

The copying is only done when using libgraal. I'd like to have this test run in a JDK without libgraal.


PR Review Comment: https://git.openjdk.org/jdk/pull/14000#discussion_r1195702132

More information about the graal-dev mailing list