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.
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.
- relates to
-
JDK-8180612 [ppc] assert failure in cpu/ppc/vm/assembler_ppc.hpp due to immediate value out of range
-
- Resolved
-
-
JDK-8180723 Compiler RTM tests fail
-
- Closed
-