RFR: 8350263: JvmciNotifyBootstrapFinishedEventTest intermittently times out

Doug Simon dnsimon at openjdk.org
Tue Feb 18 14:31:10 UTC 2025


On Tue, 18 Feb 2025 14:20:02 GMT, Yudi Zheng <yzheng at openjdk.org> wrote:

>> [JDK-8346781](https://bugs.openjdk.org/browse/JDK-8346781) changed `JVMCIServiceLocator` such that set of providers is computed eagerly in `JVMCIServiceLocator.<clinit>`. There are some JVMCI test classes that directly subclassed `JVMCIServiceLocator` which meant deadlock could occur between the main thread running the test and a JVMCI compiler thread. This PR fixes this by ensuring that `JVMCIServiceLocator` providers are separate classes from the main test class.
>
> test/hotspot/jtreg/compiler/jvmci/TestUncaughtErrorInCompileMethod.java line 89:
> 
>> 87:             "-XX:+UnlockExperimentalVMOptions",
>> 88:             "-XX:+UseJVMCICompiler", "-Djvmci.Compiler=ErrorCompiler",
>> 89:             "-XX:-UseJVMCINativeLibrary",
> 
> do we support this in a jdk build?

Not sure I understand the question: `UseJVMCINativeLibrary` is a JVMCI flag just like all other JVMCI flags.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/23679#discussion_r1959863432


More information about the hotspot-compiler-dev mailing list