JDK-6518907 : cleanup IA64 specific code in Hotspot
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: itanium
- Submitted: 2007-01-29
- Updated: 2024-09-24
- Resolved: 2013-02-02
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 8 | Other | Other |
|---|---|---|
8Fixed  |
hs25Fixed | hs25,openjdk7uFixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
There are about 40 #ifdef directives which mention IA64. (See attachment.) Recently a probable bug was noticed around line 150 of oop.inline.hpp, in IA64-specific code: It looks like the length value is garbage. On the other hand, another bug was fixed around line 1500 in graphKit.cpp, as part of 6470497, which had earlier (2002/11/05) been fixed only in an IA64 ifdef. Failure to backport this fix led to a customer VM crash. In both cases, it would probably have been better to eliminate or at least minimize the number and volume of IA64-specific #ifdefs. (And other #ifdefs for other platforms, too!) Somebody needs to make a pass through the sources and vigorously rethink, rewrite, and remove the platform-specific #ifdefs in our code.
Comments
|