JDK-8255274 : [PPC64, s390] wrong StringLatin1.indexOf version matched
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 16
- Priority: P1
- Status: Resolved
- Resolution: Fixed
- CPU: ppc,s390x
- Submitted: 2020-10-22
- Updated: 2021-12-29
- Resolved: 2020-10-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 16 |
|---|
16 b22Fixed  |
Related Reports
|
Relates :
|
Description
PPC64 and s390 currently match indexOfChar_U also for StrIntrinsicNode::L. This leads to incorrect results of StringLatin1.indexOf and alreads breaks builds: Optimizing the exploded image Error occurred during initialization of boot layer We need separate match rules for StrIntrinsicNode::U and StrIntrinsicNode::L.
Comments
|