Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8063331 | 8u45 | Filipp Zhinkin | P5 | Resolved | Fixed | b01 |
JDK-8071067 | emb-8u47 | Unassigned | P5 | Resolved | Fixed | team |
During 8030976 backport into 8u40 names of rtm_state_change and unstable_if deoptimization reasons were swapped, so now rtm_state_change is reported in compilation log as "unstable_if" and unstable_if is reported as "rtm_state_change".
In jdk9 both deopt reasons have correct names.
Affected tests:
compiler/rtm/locking/TestRTMDeoptOnHighAbortRatio.java
compiler/rtm/locking/TestRTMDeoptOnLowAbortRatio.java
compiler/rtm/locking/TestRTMLockingCalculationDelay.java
compiler/rtm/locking/TestUseRTMDeopt.java
In jdk9 both deopt reasons have correct names.
Affected tests:
compiler/rtm/locking/TestRTMDeoptOnHighAbortRatio.java
compiler/rtm/locking/TestRTMDeoptOnLowAbortRatio.java
compiler/rtm/locking/TestRTMLockingCalculationDelay.java
compiler/rtm/locking/TestUseRTMDeopt.java
- backported by
-
JDK-8063331 Names of rtm_state_change and unstable_if deoptimization reasons were swapped in 8u40
-
- Resolved
-
-
JDK-8071067 Names of rtm_state_change and unstable_if deoptimization reasons were swapped in 8u40
-
- Resolved
-