JDK-8261270 : MakeMethodNotCompilableTest fails with -XX:TieredStopAtLevel={1,2,3}
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-02-06
- Updated: 2021-02-11
- Resolved: 2021-02-07
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 17 |
|---|
17 b09Fixed  |
Related Reports
|
Relates :
|
Description
JDK-8251462 changed semantics of CompilationPolicy::highest_compile_level() and CompilationPolicy::can_be_compiled() to take into the account compiler availability due to command line flags restrictions. For example, if C2 is not available because of the TieredStopAtLevel setting, the answer to these queries will be that the highest level is 3, and that methods can't be compiled at level 4. MakeMethodNotCompilableTest.java assumes (even in the presence of the mentioned restrictions) that with tiered compilation it is always the case that both compilers can be used.
Comments
|