check that 64 bit compiler is installed properly on solaris 10

How to check that the 64 bit compiler is installed properly on solaris
10 (SunOS 5.10 Generic sun4u sparc SUNW,Sun-Blade-2500)?

$ java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

TsanChung wrote:
> How to check that the 64 bit compiler is installed properly on solaris
> 10 (SunOS 5.10 Generic sun4u sparc SUNW,Sun-Blade-2500)?
>
> $ java -version
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

Assuming you mean "64-bit JVM" instead of "64-bit compiler"
(if such a thing exists, I've not heard of it), try

file `which java`

--
Eric.Sosman-at-sun.com

On Aug 26, 10:18 pm, TsanChung wrote:
> How to check that the 64 bit compiler is installed properly on solaris
> 10 (SunOS 5.10 Generic sun4u sparc SUNW,Sun-Blade-2500)?
>
> $ java -version
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

Assuming you mean 64 bit java, try the following:

$ /usr/java/bin/sparcv9/java -version
java version "1.5.0_16"
Java(TM) Platform, Standard Edition for Business (build 1.5.0_16-b02)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_16-b02, mixed mode)

$ /usr/j2se/bin/sparcv9/java -version
java version "1.4.2_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_16-b05, mixed mode)

$ grep "sparcv9/java " /var/sadm/install/contents
/usr/j2se/bin/sparcv9/java f none 0755 root bin 87944 36532 1190019770
SUNWj3rtx/usr/j2se/jre/bin/sparcv9/java f none 0755 root bin 87944
36532 1190015296 SUNWj3rtx
/usr/jdk/instances/jdk1.5.0/bin/sparcv9/java f none 0755 root bin
83264 44135 1211968725 SUNWj5rtx
/usr/jdk/instances/jdk1.5.0/jre/bin/sparcv9/java f none 0755 root bin
83264 44135 1211968725 SUNWj5rtx

$ find /usr -type f -name java
/usr/j2se/bin/java
/usr/j2se/bin/sparcv9/java
/usr/j2se/jre/bin/java
/usr/j2se/jre/bin/sparcv9/java
/usr/jdk/instances/jdk1.5.0/bin/java
/usr/jdk/instances/jdk1.5.0/bin/sparcv9/java
/usr/jdk/instances/jdk1.5.0/jre/bin/java
/usr/jdk/instances/jdk1.5.0/jre/bin/sparcv9/java
/usr/local/bin/jvm/1.4.2_11/bin/java

Eric Sosman wrote:
> Assuming you mean "64-bit JVM" instead of "64-bit compiler"
> (if such a thing exists, I've not heard of it),

The compiler output (the byte code) is identical on 32, 64 and 77
bit computers.

It is WORA not WORA(n bit).

Arne

Arne Vajhøj wrote:
> Eric Sosman wrote:
>> Assuming you mean "64-bit JVM" instead of "64-bit compiler"
>> (if such a thing exists, I've not heard of it),
>
> The compiler output (the byte code) is identical on 32, 64 and 77
> bit computers.
>
> It is WORA not WORA(n bit).

Yes: There is only one class file format, and all JVM
implementations of whatever bit-ness digest it. But it's
conceivable, just barely, that somebody might write a Java
source so huge and intricate that javac running on a 32-bit
JVM would run out of memory trying to compile it. If so,
then somebody somewhere might have hacked up a javac that
runs on a 64-bit JVM, and that might justifiably be called
a "64-bit Java compiler."

(All right, it's a stretch that would shame Elastic Man.
But after many years of being forced to eat my words, I've
grown timid about saying "I have never seen an X, therefore
no X exists." Safer to replace the comma with a full stop
and strike all that follows ...)

--
Eric Sosman
esosman-at-ieee-dot-org.invalid

On Aug 26, 6:11*pm, Nick B wrote:
> On Aug 26, 10:18 pm, TsanChung wrote:
>
> > How to check that the 64 bit compiler is installed properly on solaris
> > 10 (SunOS 5.10 Generic sun4u sparc SUNW,Sun-Blade-2500)?
>
> > $ java -version
> > java version "1.6.0_07"
> > Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> > Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
>
> Assuming you mean 64 bit java, try the following:
>
> $ /usr/java/bin/sparcv9/java -version
> java version "1.5.0_16"
> Java(TM) Platform, Standard Edition for Business (build 1.5.0_16-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_16-b02, mixed mode)
>
> $ /usr/j2se/bin/sparcv9/java -version
> java version "1.4.2_16"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_16-b05, mixed mode)
>
> $ grep "sparcv9/java " /var/sadm/install/contents
> /usr/j2se/bin/sparcv9/java f none 0755 root bin 87944 36532 1190019770
> SUNWj3rtx/usr/j2se/jre/bin/sparcv9/java f none 0755 root bin 87944
> 36532 1190015296 SUNWj3rtx
> /usr/jdk/instances/jdk1.5.0/bin/sparcv9/java f none 0755 root bin
> 83264 44135 1211968725 SUNWj5rtx
> /usr/jdk/instances/jdk1.5.0/jre/bin/sparcv9/java f none 0755 root bin
> 83264 44135 1211968725 SUNWj5rtx
>
> $ find /usr -type f -name java
> /usr/j2se/bin/java
> /usr/j2se/bin/sparcv9/java
> /usr/j2se/jre/bin/java
> /usr/j2se/jre/bin/sparcv9/java
> /usr/jdk/instances/jdk1.5.0/bin/java
> /usr/jdk/instances/jdk1.5.0/bin/sparcv9/java
> /usr/jdk/instances/jdk1.5.0/jre/bin/java
> /usr/jdk/instances/jdk1.5.0/jre/bin/sparcv9/java
> /usr/local/bin/jvm/1.4.2_11/bin/java

Following your instructions, I think my 64 bit JVM is installed
properly.
# /usr/java/bin/sparcv9/java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
# /usr/j2se/bin/sparcv9/java -version
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_06-b03, mixed mode)
# grep "sparcv9/java " /var/sadm/install/contents
/usr/j2se/bin/sparcv9/java f none 0755 root bin 87480 5826 1106443473
SUNWj3rtx
/usr/j2se/jre/bin/sparcv9/java f none 0755 root bin 87480 5826
1106443475 SUNWj3rtx
/usr/jdk/instances/jdk1.5.0/bin/sparcv9/java f none 0755 root bin
84048 59348 1106443890 SUNWj5rtx
/usr/jdk/instances/jdk1.5.0/jre/bin/sparcv9/java f none 0755 root bin
84048 59348 1106443891 SUNWj5rtx
# find /usr -type f -name java
/usr/j2se/bin/sparcv9/java
/usr/j2se/bin/java
/usr/j2se/jre/bin/sparcv9/java
/usr/j2se/jre/bin/java
/usr/jdk/instances/jdk1.5.0/bin/java
/usr/jdk/instances/jdk1.5.0/bin/sparcv9/java
/usr/jdk/instances/jdk1.5.0/jre/bin/java
/usr/jdk/instances/jdk1.5.0/jre/bin/sparcv9/java
/usr/jdk/instances/jdk1.6.0_07/jre/bin/java
/usr/jdk/instances/jdk1.6.0_07/jre/bin/sparcv9/java
/usr/jdk/instances/jdk1.6.0_07/bin/java
/usr/jdk/instances/jdk1.6.0_07/bin/sparcv9/java

# cd /usr/jdk/jdk1.6.0_07
# java -client -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

# bin/sparcv9/java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
# bin/java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

Why 64-Bit VM is "Server" but not "Client"?

TsanChung wrote:
> # cd /usr/jdk/jdk1.6.0_07
> # java -client -version
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
>
> # bin/sparcv9/java -version
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
> # bin/java -version
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
>
> Why 64-Bit VM is "Server" but not "Client"?

You will need to ask SUN to get an authoritative answer, but
it seems as a good guess that SUN so far don't feel that
a client type app needs so much memory that 64 bit is
necessary.

Arne

Arne Vajhøj wrote:
> TsanChung wrote:
>> # cd /usr/jdk/jdk1.6.0_07
>> # java -client -version
>> java version "1.6.0_07"
>> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
>> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
>>
>> # bin/sparcv9/java -version
>> java version "1.6.0_07"
>> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
>> Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
>> # bin/java -version
>> java version "1.6.0_07"
>> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
>> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
>>
>> Why 64-Bit VM is "Server" but not "Client"?
>
> You will need to ask SUN to get an authoritative answer, but
> it seems as a good guess that SUN so far don't feel that
> a client type app needs so much memory that 64 bit is
> necessary.

And I believe that the 32 bit JVM on 64 bit Solaris can
use almost 4 GB for heap.

Arne

On Aug 28, 6:29*pm, Arne Vajhøj wrote:
> Arne Vajhøj wrote:
> > TsanChung wrote:
> >> # cd /usr/jdk/jdk1.6.0_07
> >> # java -client -version
> >> java version "1.6.0_07"
> >> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> >> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
>
> >> # bin/sparcv9/java -version
> >> java version "1.6.0_07"
> >> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> >> Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
> >> # bin/java -version
> >> java version "1.6.0_07"
> >> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> >> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
>
> >> Why 64-Bit VM is "Server" but not "Client"?
>
> > You will need to ask SUN to get an authoritative answer, but
> > it seems as a good guess that SUN so far don't feel that
> > a client type app needs so much memory that 64 bit is
> > necessary.
>
> And I believe that the 32 bit JVM on 64 bit Solaris can
> use almost 4 GB for heap.

Sun has documented this. The JVM defaults to "server" mode on "server-
class" machines.

You can override that with the command-line options.

--
Lew