RFR(XS): 8232616: JVMCI_lock fails to get initialized when cds is disabled
coleen.phillimore at oracle.com
coleen.phillimore at oracle.com
Mon Oct 21 18:37:25 UTC 2019
Looks good to me also.
Coleen
On 10/18/19 8:35 AM, Jie Fu wrote:
> Hi all,
>
> JBS: https://bugs.openjdk.java.net/browse/JDK-8232616
> Webrev: http://cr.openjdk.java.net/~jiefu/8232616/webrev.00/
>
> When cds was disabled, many tests in compiler/aot and compiler/jvmci
> crashed due to SIGSEGV in Mutex::unlock().
> For the list of failing tests, please refer to the JBS.
>
> The reason for these crashes is that JVMCI_lock fails to get
> initialized when cds is disabled [1].
>
> I suggest to fix this bug since aot and jvmci seem not to be dependent
> on cds.
> Could you please review it and give me some advice?
>
> Testing:
> - The list of failing tests due to this bug on Linux/x64
> - make test TEST="tier1" CONF=server-release on Linux/x64
>
> Thanks a lot.
> Best regards,
> Jie
>
> [1]
> http://hg.openjdk.java.net/jdk/jdk/file/2e0462f4cf4e/src/hotspot/share/runtime/mutexLocker.cpp#l339
>
>
More information about the hotspot-runtime-dev
mailing list