RFR: 8255595: delay_to_keep_mmu passes wrong arguments to Monitor wait
Kim Barrett
kbarrett at openjdk.java.net
Fri Oct 30 04:12:42 UTC 2020
On Thu, 29 Oct 2020 15:42:05 GMT, Albert Mingkun Yang <ayang at openjdk.org> wrote:
>> Please review this trivial fix of the second argument in a call to MonitorLocker::wait. Because the locker is constructed as no-safepoint-checking, the improper second argument is ignored rather than possibly going into an unexpected state.
>
> Marked as reviewed by ayang (Author).
> I wonder if it's feasible and/or worthwhile to use `clang-tidy` (or sth similar) to detect this kind of error in existing code and prevent it from happening again in new code.
See https://bugs.openjdk.java.net/browse/JDK-8255596
-------------
PR: https://git.openjdk.java.net/jdk/pull/934
More information about the hotspot-gc-dev
mailing list