JDK-4295833 : Provide full 64 bit support
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.1.6,1.1.7,1.2.0,1.2.2,1.3.0,1.4.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS:
    generic,solaris_2.5.1,solaris_7,solaris_8,windows_nt generic,solaris_2.5.1,solaris_7,solaris_8,windows_nt
  • CPU: generic,x86,sparc
  • Submitted: 1999-12-01
  • Updated: 2012-10-13
  • Resolved: 2000-12-12
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 Availabitlity Release.

To download the current JDK release, click here.
Other
1.4.0 betaFixed
Related Reports
Duplicate :  
Duplicate :  
Description
Merlin should provide full 64 bit support.

This includes making sure all native platform APIs (JNI, JVMDI, JVMPI, etc)
are well defined at 64 bits, and scrubbing all shared, solaris, and win32
native source code to be 64 bit clean. 

The initial delivery of Merlin will include a 64 bit version of the Java
HotSpot(TM) VM implementation for Solaris on Sparc v9.

Support will be added later for Linux on IA-64 and Windows 2000 on IA-64.
Since 64 bit support has as no API visibility, it can be added in maintenace releases.

In all cases the emphasis will be on the Server system. The client system will
eventually be adjusted as well, but the client system is not primarily targeting
systems that require 64 bit addressing (that's why it is a client, after
all). Thus primary focus will be on the server platform.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin FIXED IN: merlin-beta INTEGRATED IN: merlin-beta
2004-06-14

EVALUATION There's no i386 architecture supporting 64 bits, nor is Windows NT, Windows 95, 98, 2000 supporting it. A 64 bit port for Merced is not yet under way and is unlikely to complete for the current Merlin timeframe even if started now. There is a 64 bit Intel-compatible CPU from AMD (Athlon), but no widely used OS is supporting 64 bit applications on this machine. For our purpose, the goal should be on a 64 bit ready Java HotSpot Virtual Machine with Server Compiler. The Client Compiler should eventually be adjusted as well, but the Client is not targeting machines which would require 64 bits (that's why it is a client, after all). Most probably, adjusting a 64 bit Sparc Solaris implementation can be adjusted relatively quickly to a 64 bit Linux Sparc implementation, since all the OS specific factoring already exists. (see also: http://www.ultralinux.org) robert.griesemer@Eng 2000-02-24 Name: db100478 Date: 09/08/2000 Committing to merlin release ======================================================================
2000-02-24