JDK-6577429 : java -d64 should work consistently (inconsistent behavior on windows-amd64)
  • Type: Bug
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 6u3
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2007-07-05
  • Updated: 2010-04-02
  • Resolved: 2007-07-09
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.
JDK 6
6u3Resolved
Related Reports
Relates :  
JDK-4942878 - Don't make "java -client" be an error on 64-bit platforms
Relates :  
JDK-6277269 - windows-amd64 launcher should accept -d64
Relates :  
JDK-6234127 - AMD64: java -client -version shows Error message with windows-amd64
Description
Currently (with jdk 1.6.0_03 b01), -d64 option does not work on windows :

%MYDRIVE%\jdk\1.6.0_03\promoted\all\b01\binaries\windows-amd64\bin>java -d64 -version
Unrecognized option: -d64
Could not create the Java virtual machine.

If jvm.cfg (under $JAVA_HOME\jre\lib\amd64) is modified as :
-d64 ALIASED_TO -server

or

-d64 IGNORE

then it works as expected.

To be consistent with other 64 bit platforms (solaris-sparcv9, solaris-amd64 and linux-amd64), windows-amd64 binaries also should support -d64 option.
Comments
EVALUATION The -d64 option does not work in JDK 6 under windows; it is recognized in JDK 7 (6277269). This can be changed to work on JDK 6 too, but the current behavior is documented and correct. Closing as not a bug.
09-07-2007