JDK-8268571 : C2: change order of locks optimizations
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 18
  • Priority: P4
  • Status: In Progress
  • Resolution: Unresolved
  • Submitted: 2021-06-10
  • Updated: 2021-07-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8268347 - C2: nested locks optimization may create unbalanced monitor enter/exit code
Description
As JDK-8268347 showed remarking coarsened locks may lead to incorrect code. To avoid that I suggest to execute locks coarsening after EA and nested locks optimizations.
Comments
The idea is to delay coarsening optimization after EA and nested locks marking. An other idea is to instead of bailout and recompilation without coarsening mark unbalanced coarsened locks/unlocks back to Regular lock only in unbalanced group. This way coarsened locks/unlocks group which are balanced will be eliminated.
28-06-2021