[13] RFR(L) 8220623: [JVMCI] Update JVMCI to support JVMCI based Compiler compiled into shared library
Tom Rodriguez
tom.rodriguez at oracle.com
Fri Mar 29 16:44:50 UTC 2019
> This is the original fix I had for this:
>
> CompilerThread* ct = (CompilerThread*) thr;
> if (ct->compiler() == NULL || !ct->compiler()->is_jvmci() JVMCI_ONLY(|| !UseJVMCINativeLibrary)) {
> num_active_compiler_thread++;
> } else {
> // When using a compiler in a JVMCI shared library, it's possible
> // for one compiler thread to grab a lock in the shared library,
> // enter HotSpot and go to sleep on the shutdown safepoint. Another
> // JVMCI shared library compiler thread can then attempt to grab the
> // lock and thus never make progress.
> }
>
> which is probably the right one. I hadn’t realized that a JavaGraal
> (as opposed to libgraal) JVMCI compiler thread blocked on a lock will be in
> the blocked state, not in the _thread_in_native state.
I think it would be ok to go back to your original fix.
tom
More information about the graal-dev
mailing list