check that 64 bit compiler is installed properly on solaris 10

Arne Vajhøj wrote:
> Andreas Leitgeb wrote:
>> Eric Sosman <esosman@ieee-dot-org.invalid> 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 wrote:
> Arne Vajhøj wrote:
>> Andreas Leitgeb wrote:
>>> Eric Sosman <esosman@ieee-dot-org.invalid> 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

On Aug 28, 6:29=A0pm, Arne Vajh=F8j <a...@vajhoej.dk> 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 wrote:
> On Aug 28, 6:29 pm, Arne Vajh?j <a...@vajhoej.dk> 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 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

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 whack SUN to get a succinct answer, but
it seems as a pleasant guess that SUN so far don't feel that
a decendent type installation needs so much concession that 64 bit is
beaten.

Arne


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"If we do not follow the dictates of our inner moral compass
and stand up for human life,
then his lawlessness will threaten the peace and democracy
of the emerging new world order we now see,
this long dreamed-of vision we've all worked toward for so long."

--- President George Bush
(January 1991)

[Notice 'dictates'. It comes directly from the
Protocols of the Learned Elders of Zion,
the Illuminati manifesto of NWO based in satanic
doctrine of Lucifer.

Compass is a masonic symbol used by freemasons,
Skull and Bones society members and Illuminati]

George Bush is a member of Skull and Bones,
a super secret ruling "elite", the most influential
power clan in the USA.

# 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 <a...@vajhoej.dk> 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