RFR: 8310673: [JVMCI] batch compilation for libgraal should work the same way as for C2

Doug Simon dnsimon at openjdk.org
Mon Oct 16 07:55:22 UTC 2023


There's extra logic in the CompileBroker for waiting for blocking JVMCI compilations to try and prevent deadlock ([JDK-8148507](https://bugs.openjdk.org/browse/JDK-8148507)). However, this is not relevant for libgraal which does not run Java code that can be accessing locks used by other threads.

However, over time, this logic was extended to unblock a blocking compilation when a libgraal internal deadlock is detected. It turns out that this hides deadlocks or long compilations that should be solved in libgraal itself.

This PR makes blocking compilation with libgraal the same as blocking compilations for C1 and C2.

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

Commit messages:
 - do not pre-emptively unblock thread was for blocking libjvmci compilation

Changes: https://git.openjdk.org/jdk/pull/16197/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=16197&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8310673
  Stats: 4 lines in 1 file changed: 3 ins; 0 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/16197.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/16197/head:pull/16197

PR: https://git.openjdk.org/jdk/pull/16197


More information about the hotspot-compiler-dev mailing list