RFR: 8258015: [JVMCI] JVMCI_lock shouldn't be held while initializing box classes
Doug Simon
dnsimon at openjdk.java.net
Thu Dec 10 11:28:36 UTC 2020
On Thu, 10 Dec 2020 09:26:10 GMT, Jie Fu <jiefu at openjdk.org> wrote:
>> src/hotspot/share/jvmci/jvmci.cpp line 133:
>>
>>> 131: return;
>>> 132: }
>>> 133: MutexLocker locker(JVMCI_lock);
>>
>> This lock is required in the case where this is not called from `AOTLoader::initialize_box_caches` to ensure only one JVMCI compiler thread does the lazy initialization.
>> I can fix this if you'd like me to put up a separate PR.
>
> OK. Please feel free to do so.
> Thanks.
I've opened https://github.com/openjdk/jdk/pull/1730.
-------------
PR: https://git.openjdk.java.net/jdk/pull/1727
More information about the hotspot-compiler-dev
mailing list