-
Bug
-
Resolution: Fixed
-
P4
-
13
-
b19
MutexLockerEx is almost identical to MutexLocker, except that it allows NULL and to pass a safepoint checking parameter. These two branches seem like an uninteresting distinction for minimal or likely no performance benefit. The operation takes a lock which will dwarf any predicted branches.
Also, there's a corresponding MutexUnlocker/MutexLockerEx which seemes even less necessary for performance.
Also, there's a corresponding MutexUnlocker/MutexLockerEx which seemes even less necessary for performance.
- relates to
-
JDK-8313202 MutexLocker should disallow null Mutexes
- Resolved