JDK-8252292 : 8240795 may cause anti-dependence to be missed
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 15,16
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2020-08-25
- Updated: 2021-01-13
- Resolved: 2020-08-27
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 15 | JDK 16 |
|---|---|
| 15.0.2Fixed | 16 b14Fixed  |
Related Reports
|
Relates :
|
Description
I see that with the following loop
for (int i = 0; i < stop; i ++) {
if (flag1) {
System.arraycopy(src, 0, dst, 0, j);
v = dst[9];
if (flag2) {
src[9] = 0x42;
}
}
}
the value of v that's loaded can be wrong (0x42 when flag2 is true) because of missing anti-dependence between the load (once transformed to a load on src) and store.
Comments
|