JDK-8202611 : [GRAAL] Exclude CMS GC testing from runs with Graal
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 11
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2018-05-03
- Updated: 2021-10-05
- Resolved: 2018-06-08
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 11 |
|---|
11 b18Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
JDK-8184349 handles Hotspot changes to add check that Graal support GC and exit on error if it does not. It also added @requires !vm.graal.enabled into tests which use only CMS. Unfortunately some tests are more complicated - have several @run commands for different GCs or fork new process for each GC. It requires complex changes and I want to separate them from already big changes for JDK-8184349.
Comments
|