-
Bug
-
Resolution: Not an Issue
-
P2
-
None
-
1.4.1
-
itanium
-
generic
On solsparc in order to launch a 64-bit VM , we could use
-d64, -server -d64
The same should work on Itanium bits as well
eventhough the default on Itanium is 64-bit VM)
However if I specify the d64 arguement , the jvm is not started
Itanium bits used : build 1.4.1-internal-bobv_14_mar_2002_03_48
---- see below ---------
/net/taloraan/export/vsn/VM/hopper/testing-64/jdk-64/jdk1.4.1_linux_ia64/bin/jav
a -d64 -version
> Unrecognized option: -d64
> Could not create the Java virtual machine.
>
/net/taloraan/export/vsn/VM/hopper/testing-64/jdk-64/jdk1.4.1_linux_ia64/bin/jav
a -d64 -server -version
> Unrecognized option: -d64
> Could not create the Java virtual machine.
>
/net/taloraan/export/vsn/VM/hopper/testing-64/jdk-64/jdk1.4.1_linux_ia64/bin/jav
a -server -version
> java version "1.4.1-internal"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.4.1-internal-bobv_14_mar_2002_03_48)
> Java HotSpot(TM) 64-Bit Core VM (build 1.4-internal, interpreted mode)
>
###@###.### 2002-04-10
-d64, -server -d64
The same should work on Itanium bits as well
eventhough the default on Itanium is 64-bit VM)
However if I specify the d64 arguement , the jvm is not started
Itanium bits used : build 1.4.1-internal-bobv_14_mar_2002_03_48
---- see below ---------
/net/taloraan/export/vsn/VM/hopper/testing-64/jdk-64/jdk1.4.1_linux_ia64/bin/jav
a -d64 -version
> Unrecognized option: -d64
> Could not create the Java virtual machine.
>
/net/taloraan/export/vsn/VM/hopper/testing-64/jdk-64/jdk1.4.1_linux_ia64/bin/jav
a -d64 -server -version
> Unrecognized option: -d64
> Could not create the Java virtual machine.
>
/net/taloraan/export/vsn/VM/hopper/testing-64/jdk-64/jdk1.4.1_linux_ia64/bin/jav
a -server -version
> java version "1.4.1-internal"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.4.1-internal-bobv_14_mar_2002_03_48)
> Java HotSpot(TM) 64-Bit Core VM (build 1.4-internal, interpreted mode)
>
###@###.### 2002-04-10