JDK-8141624 : Limit calculation of pre loop during super word optimization is wrong
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2015-11-06
- Updated: 2020-04-07
- Resolved: 2015-11-11
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 b96Fixed  |
Related Reports
|
Relates :
|
Description
gunter.haug@sap.com reported the following problem: The variable "MemNode* best_align_to_mem_ref" is hidden by a second declaration of a variable with the same name in an inner block of the function "SuperWord::find_adjacent_refs()". This leads to unaligned accesses in generated code. While many platforms handle these correctly (slower, though), Itanium and potentially other platforms which don't allow unaligned access will crash.