JDK-8221083 : [ppc64] Wrong oop compare in C1-generated code
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 11,12,13
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- CPU: ppc
- Submitted: 2019-03-19
- Updated: 2022-04-25
- Resolved: 2019-03-26
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 | JDK 12 | JDK 13 |
|---|---|---|
| 11.0.4Fixed | 12.0.2Fixed | 13 b14Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The C1 generated code for comparing two oops erroneously emits a 32-bit instead of an 64-bit compare instruction. Because oops are only compared for equality/inequality, this bug only becomes manifests for oops which are equal in their 32 least-significant bits but unequal otherwise. This means the two oops have to be exactly 4GB apart from each other in the heap or their 32 least significant bits have to be zero when compared to 'null'. This makes the occurrence of this bug extremely unlikely, but when it happens, the consequences are usually a semantically wrong program execution and not a crash, which makes it very hard to detect.
Comments
|