JDK-8152483 : Fix a couple of tests that are being incorrectly run on C1 after jigsaw M3
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-03-22
- Updated: 2016-03-31
- Resolved: 2016-03-23
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 9 |
|---|
9 b112Fixed  |
Related Reports
|
Duplicate :
|
Sub Tasks
|
JDK-8152484 :
|
Description
compiler/unsafe/UnsafeGetConstantField.java is failing during the synching of jigsaw M3 into jdk9/hs. This test should not be run in C1, but it is getting run due to a problem with filtering in the latest version of jtreg. Test is being fixed to run only on server VM. compiler/unsafe/UnsafeGetConstantField.java is also being fixed