The BasicLock and OMCaches shouldn't be used for deoptimization. It's an unnecessary optimization and confuses the code when BasicLock cache is set and needs to be unset.
The OMCache has some unnecessary shuffling if the lock is found in the BasicLock cache. The code to read caches can be made less duplicative.
The BasicLock cache needs to be cleared if a deflated monitor is found. That's done in the right place now.
Some comments need to be added.
The OMCache has some unnecessary shuffling if the lock is found in the BasicLock cache. The code to read caches can be made less duplicative.
The BasicLock cache needs to be cleared if a deflated monitor is found. That's done in the right place now.
Some comments need to be added.
- relates to
-
JDK-8339114 DaCapo xalan performance with -XX:+UseObjectMonitorTable
-
- Closed
-
- links to
-
Commit(master)
openjdk/jdk/9ead2b75
-
Review(master)
openjdk/jdk/24545