|
> IBM has claimed that optimizing at level 40 should make Java perform as > though it were compiled. I think that's stretching it a bit. This is true. If you look at the reported documentation to support this, the Java bytecode (i.e. the binary Java object code that the JVM interprets) is converted to w-code (the intermediate ILE representation format) and then passed to the backend program translator CUBE3. CUBE3 then creates a PowerPC RISC instruction stream from the w-code and creates a true RISC compiled binary program object. On executing your new optimized Java program, the JVM under the covers does a looksee to find out if the source Java object differs from the native RISC object, if not it runs the native object and thus you *are* running compiled code, at compiled code speed. Very similar to the JIT compile JVM support on Windows/Unix. --phil +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.