JDK-8184800 : Streamline RTM flag validity testing with generic flag testing support
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 10
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- CPU: x86,ppc
- Submitted: 2017-07-18
- Updated: 2017-08-25
- Resolved: 2017-07-20
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.
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.
| JDK 10 |
|---|
10 b21Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
RTM was implemented before specifying ranges for flags was established in openJdk. It has custom checks implemented per platform in vm_version_<cpu>.cpp as well as tests for these checks in compiler/rtm/cli. 8180612 added ranges for a row of RTM flags. Tests for RTMAbortRation and RTMTotalCountIncrRate now fail, because the range check failure message is different. This change removes the custom checks, implements a generic method RTMTotalCountIncrRateConstraintFunc() and updates the tests. Some tests are now superfluous as the ranges will be tested by TestOptionsWithRanges.
Comments
|