JDK-6917698 : os::is_allocatable Zero fix for 32-bit platforms
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs17
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-01-18
- Updated: 2012-10-08
- Resolved: 2010-01-28
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 6 | JDK 7 | Other |
|---|---|---|
6u21Fixed  |
7Fixed |
hs17Fixed |
Description
Gary Benson wrote: Hi all, Recent changes in arguments.cpp mean that os::allocatable_physical_memory is now always called at VM startup. On 32-bit platforms this calls os::is_allocatable which was not implemented in Zero. This webrev implements this: http://cr.openjdk.java.net/~gbenson/zero-is_allocatable/ The implementation provided is essentially a copy of the one from os_linux_x86.cpp. It was contributed by Edward Nevill, an SCA signatory. I modified his contribution by replacing the AMD64 conditional with _LP64 to make the code generic. Note that I added 2009 to the copyright header as well as 2010. This was intentional: I modified that file several times in 2009, and forgot to update the copyright each time :/ There is no bug filed for this issue yet. Cheers, Gary
Comments
|