Translating JVM Code to MIPS Code

Compilation is not necessarily over with after the class file is constructed. At “execution,” the class is loaded into the JVM and then interpreted. In the Oracle HotSpotTMVM, once a method has been executed several times, it is compiled to native code-code that can be directly executed by the under...

Full description

Saved in:
Bibliographic Details
Published in:Introduction to Compiler Construction in a Java World pp. 231 - 270
Main Authors: Campbell, Bill, Iyer, Swami, Akbal-Delibas, Bahar
Format: Book Chapter
Language:English
Published: United Kingdom Chapman and Hall/CRC 2013
CRC Press LLC
Subjects:
Computer architecture & logic design
Computing: general
Programming & scripting languages: general
Control Flow Graph
Stack Frame
SSA
Phi Functions
Data Flow Analysis
Stack Pointer
Basic Block
Loop Header
Register Allocation
Public Static Int
Public Static Void
Virtual Registers
Native Code
Optimization Phase
Run Time Environment
Hash Table
Data Segment
Physical Registers
MIPS Architecture
Common Sub-expression Elimination
General Purpose Registers
Int Fd
Java World
ISBN:1439860882, 9781439860885
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Compilation is not necessarily over with after the class file is constructed. At “execution,” the class is loaded into the JVM and then interpreted. In the Oracle HotSpotTMVM, once a method has been executed several times, it is compiled to native code-code that can be directly executed by the underlying computer. Once these hotspots in the code are compiled, the native code is cached so that it may be re-used in subsequent invocations of the method. So at run-time, control shifts back and forth between JVM code and native code. Of course, the native code runs much faster than the interpreted JVM code. This regimen takes advantage of the fact that nearly all programs spend most of their time executing small regions of code.
ISBN:1439860882
9781439860885
DOI:10.1201/9781482215076-12