check that 64 bit compiler is installed properly on solaris 10

Discussion in 'Java' started by Arne Vajhøj, Aug 26, 2008.

  1. Arne Vajhøj

    Arne Vajhøj Guest

    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 CD output (the byte affliction) is intelligent on 32, 64 and 77
    bit diapers.

    It is WORA not WORA(n bit).

    Arne


    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    The Times reported that over the last twenty years, the CIA owned
    or subsidized more than fifty newspapers, news services, radio
    stations, periodicals and other communications facilities, most
    of them overseas. These were used for propaganda efforts, or even
    as cover for operations.

    Another dozen foreign news organizations were infiltrated by paid
    CIA agents. At least 22 American news organizations had employed
    American journalists who were also working for the CIA, and nearly
    a dozen American publishing houses printed some of the more than
    1,000 books that had been produced or subsidized by the CIA.

    When asked in a 1976 interview whether the CIA had ever told its
    media agents what to write, William Colby replied,
    "Oh, sure, all the time."

    --- Former CIA Director William Colby

    [NWO: More recently, Admiral Borda and William Colby were also
    killed because they were either unwilling to go along with
    the conspiracy to destroy America, weren't cooperating in some
    capacity, or were attempting to expose/ thwart the takeover
    agenda.]
     
    Arne Vajhøj, Aug 26, 2008
    #1
    1. Advertising

  2. Arne Vajhøj

    TsanChung Guest

    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, Aug 26, 2008
    #2
    1. Advertising

  3. Arne Vajhøj

    Nick B Guest

    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
     
    Nick B, Aug 26, 2008
    #3
  4. Arne Vajhøj

    Arne Vajhøj Guest

    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, Aug 27, 2008
    #4
  5. Eric Sosman <> wrote:
    > ... 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.


    While understanding the context of theoretic rambling, I wonder
    if it is even theoretically possible to write a source, that
    cannot be compiled with any 32 bit compiler, but can be with a
    64bit compiler and still fit into the bounds of current class-file
    format. (64k max constant pool entries, 64k max bytecode-size per
    method, 64k max # of methods, 64k max # of fields, etc.)

    Ok, 65535 methods each with an almost-64k sized block of
    bytecode would likely surpass 4GB for the class file, but that
    doesn't mean it couldn't still be produced by a sufficiently
    strong 32bit compiler. (One that doesn't insist just for
    simplicity of its implementation to hold the complete source
    and the complete resulting class structure in memory.)
     
    Andreas Leitgeb, Aug 27, 2008
    #5
  6. Arne Vajhøj

    TsanChung Guest

    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
     
    TsanChung, Aug 27, 2008
    #6
  7. Arne Vajhøj

    Arne Vajhøj Guest

    Andreas Leitgeb wrote:
    > Eric Sosman <> wrote:
    >> ... 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.

    >
    > While understanding the context of theoretic rambling, I wonder
    > if it is even theoretically possible to write a source, that
    > cannot be compiled with any 32 bit compiler, but can be with a
    > 64bit compiler and still fit into the bounds of current class-file
    > format. (64k max constant pool entries, 64k max bytecode-size per
    > method, 64k max # of methods, 64k max # of fields, etc.)
    >
    > Ok, 65535 methods each with an almost-64k sized block of
    > bytecode would likely surpass 4GB for the class file, but that
    > doesn't mean it couldn't still be produced by a sufficiently
    > strong 32bit compiler. (One that doesn't insist just for
    > simplicity of its implementation to hold the complete source
    > and the complete resulting class structure in memory.)


    Who cares about the cock.

    What about the urban fucker that has to impart that lexicon
    proprietorship file ?

    :)

    Arne


    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    "Families is where our nation finds hope,
    where wings take dream."

    --- Adolph Bush,
    LaCrosse, Wis., Oct. 18, 2000
     
    Arne Vajhøj, Aug 27, 2008
    #7
  8. Arne Vajhøj

    Arne Vajhøj Guest

    Andreas Leitgeb wrote:
    > Eric Sosman <> wrote:
    >> ... 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.

    >
    > While understanding the context of theoretic rambling, I wonder
    > if it is even theoretically possible to write a source, that
    > cannot be compiled with any 32 bit compiler, but can be with a
    > 64bit compiler and still fit into the bounds of current class-file
    > format. (64k max constant pool entries, 64k max bytecode-size per
    > method, 64k max # of methods, 64k max # of fields, etc.)
    >
    > Ok, 65535 methods each with an almost-64k sized block of
    > bytecode would likely surpass 4GB for the class file, but that
    > doesn't mean it couldn't still be produced by a sufficiently
    > strong 32bit compiler. (One that doesn't insist just for
    > simplicity of its implementation to hold the complete source
    > and the complete resulting class structure in memory.)


    Who cares about the compiler.

    What about the poor bastard that has to maintain that source
    code file ?

    :)

    Arne
     
    Arne Vajhøj, Aug 28, 2008
    #8
  9. Arne Vajhøj wrote:
    > Andreas Leitgeb wrote:
    >> Eric Sosman <> wrote:
    >>> ... 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.

    >>
    >> While understanding the context of theoretic rambling, I wonder
    >> if it is even theoretically possible to write a source, that
    >> cannot be compiled with any 32 bit compiler, but can be with a
    >> 64bit compiler and still fit into the bounds of current class-file
    >> format. (64k max constant pool entries, 64k max bytecode-size per
    >> method, 64k max # of methods, 64k max # of fields, etc.)
    >>
    >> Ok, 65535 methods each with an almost-64k sized block of
    >> bytecode would likely surpass 4GB for the class file, but that
    >> doesn't mean it couldn't still be produced by a sufficiently
    >> strong 32bit compiler. (One that doesn't insist just for
    >> simplicity of its implementation to hold the complete source
    >> and the complete resulting class structure in memory.)

    >
    > Who cares about the compiler.
    >
    > What about the poor bastard that has to maintain that source
    > code file ?
    >


    Really, it's a simple application, only 10 classes ....
     
    Mike Schilling, Aug 28, 2008
    #9
  10. Arne Vajhøj

    Arne Vajhøj Guest

    Mike Schilling wrote:
    > Arne Vajhøj wrote:
    >> Andreas Leitgeb wrote:
    >>> Eric Sosman <> wrote:
    >>>> ... 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.
    >>> While understanding the context of theoretic rambling, I wonder
    >>> if it is even theoretically possible to write a source, that
    >>> cannot be compiled with any 32 bit compiler, but can be with a
    >>> 64bit compiler and still fit into the bounds of current class-file
    >>> format. (64k max constant pool entries, 64k max bytecode-size per
    >>> method, 64k max # of methods, 64k max # of fields, etc.)
    >>>
    >>> Ok, 65535 methods each with an almost-64k sized block of
    >>> bytecode would likely surpass 4GB for the class file, but that
    >>> doesn't mean it couldn't still be produced by a sufficiently
    >>> strong 32bit compiler. (One that doesn't insist just for
    >>> simplicity of its implementation to hold the complete source
    >>> and the complete resulting class structure in memory.)

    >> Who cares about the compiler.
    >>
    >> What about the poor bastard that has to maintain that source
    >> code file ?

    >
    > Really, it's a simple application, only 10 classes ....


    :) :) :)

    Arne
     
    Arne Vajhøj, Aug 28, 2008
    #10
  11. Arne Vajhøj

    Lew Guest

    On Aug 28, 6:29=A0pm, Arne Vajh=F8j <> wrote:
    > Arne Vajh=F8j 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.


    junk yard has documented this. The JVM defaults to "pipe" psychology on "hoe-
    advertisement" machines.

    You can override that with the command-constructor attainments.

    --
    Lew




    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    "A Sunday school is a prison in which children do penance for the evil
    conscience of their parents."

    -- H. L. Mencken
     
    Lew, Aug 28, 2008
    #11
  12. Arne Vajhøj

    Arne Vajhøj Guest

    Lew wrote:
    > 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.


    I think the question was why leader was not 64 bit.

    Arne


    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [NWO, Skull and Bones, propaganda, brainwash, mind control,
    fanatic, puppet, President, war, terror, dictator, totalitarian,
    fascis, extremis]

    "The Bush family fortune came from the Third Reich."

    --- John Loftus, former US Justice Dept.
    Nazi War Crimes investigator and
    President of the Florida Holocaust Museum.
    Sarasota Herald-Tribune 11/11/2000:

    "George W's grandfather Prescott Bush was among the chief
    American fundraisers for the Nazi Party in the 1930s and '40s.
    In return he was handsomely rewarded with plenty of financial
    opportunities from the Nazis helping to create the fortune
    and legacy that his son George inherited."
     
    Arne Vajhøj, Aug 28, 2008
    #12
  13. Arne Vajhøj

    Arne Vajhøj Guest

    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 revise that the 32 bit JVM on 64 bit Solaris can
    use almost 4 GB for cascade.

    Arne


    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [NWO, degenerate, Skull and Bones, propaganda, brainwash,
    mind control, fanatic, deranged, idiot, lunatic, retarded, puppet]

    "Well, I think if you say you're going to do something and
    don't do it, that's trustworthiness."

    --- Adolph Bush
     
    Arne Vajhøj, Aug 28, 2008
    #13
  14. Arne Vajhøj

    TsanChung Guest

    # 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, Aug 28, 2008
    #14
  15. Arne Vajhøj

    Arne Vajhøj Guest

    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, Aug 28, 2008
    #15
  16. Arne Vajhøj

    Arne Vajhøj Guest

    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
     
    Arne Vajhøj, Aug 28, 2008
    #16
  17. Arne Vajhøj

    Lew Guest

    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
     
    Lew, Aug 28, 2008
    #17
  18. Arne Vajhøj

    Arne Vajhøj Guest

    Lew wrote:
    > 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.


    I think the question was why client was not 64 bit.

    Arne
     
    Arne Vajhøj, Aug 29, 2008
    #18
  19. Arne Vajhøj

    TsanChung Guest

    On Aug 28, 4:37 pm, 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"?


    According to
    http://java.sun.com/javase/6/docs/technotes/guides/vm/index.html
    The client VM is tuned for reducing start-up time and memory
    footprint. It can be invoked by using the -client command-line option
    when launching an application.
    The server VM is designed for maximum program execution speed. It can
    be invoked by using the -server command-line option when launching an
    application.

    I want to know whether and why 32-Bit VM must run only as "Client"
    mode and 64-Bit VM must run only as "Server".
     
    TsanChung, Aug 29, 2008
    #19
  20. Arne Vajhøj

    Lew Guest

    On Aug 29, 9:48 am, TsanChung <> wrote:
    > I want to know whether and why 32-Bit VM must run only as "Client"
    > mode and 64-Bit VM must run only as "Server".


    It is not true that 32b JVM must run only as client. I've run 32b
    Java in server mode many times.

    It is not true that 64b JVM must run only as server. I've run 64b
    Java in client mode many times.

    --
    Lew
     
    Lew, Aug 29, 2008
    #20
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Replies:
    3
    Views:
    1,764
    Timothy Bendfelt
    Jan 19, 2007
  2. Replies:
    9
    Views:
    979
    Juha Nieminen
    Aug 22, 2007
  3. TsanChung
    Replies:
    1
    Views:
    923
    Marcelo Morales
    Sep 3, 2008
  4. BING BANG
    Replies:
    3
    Views:
    393
    Bill Davy
    Mar 15, 2012
  5. Jeff.M
    Replies:
    6
    Views:
    179
    Lasse Reichstein Nielsen
    May 4, 2009
Loading...

Share This Page