[672] in java-interest
a dumb native code question
daemon@ATHENA.MIT.EDU (Michael Mills 21728)
Wed Jul 12 18:46:16 1995
From: ekim@nyquist.bellcore.com (Michael Mills 21728)
To: java-interest@java.sun.com
Date: Wed, 12 Jul 1995 17:21:47 -0400 (EDT)
Hi,
There has been some discussion of converting Java bytecode to
sparc assembler and to C++. I am a little confused. From looking at the Java
white paper I have been under the impression that at some point
Java would do this for me on the fly. Does the white paper imply that this
will be a standard Java feature?
Thanks,
Mike
PS.
I have included a section from the white paper below:
High Performance
While the performance of interpreted bytecodes is usually more than adequate,
there are situations where higher performance is required. The bytecodes can be
translated on the fly (at runtime) into machine code for the particular CPU the
application is running on. For those accustomed to the normal design of a
compiler and dynamic loader, this is somewhat like putting the final machine code
generator in the dynamic loader.
The bytecode format was designed with generating machine codes in mind, so the
actual process of generating machine code is generally simple. Reasonably good
code is produced: it does automatic register allocation and the compiler does some
optimization when it produces the bytecodes.
In interpreted code we're getting about 300,000 method calls per second on an
Sun Microsystems SPARCStation 10. The performance of bytecodes converted to
machine code is almost indistinguishable from native C or C++.
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
