Episode 144: The Maxine Research Virtual Machine with Doug Simon

Optimizing Compiler

The Maxine VM's optimizing compiler is central to its architecture, distinguishing it from traditional interpreters. Doug Simon explains that Maxine builds everything on top of this compiler, allowing VM semantics to be expressed in Java code. This approach contrasts with the hand-coded implementations in other JVMs like HotSpot. The Maxine VM uses a fast template-based JIT compiler to overcome the slow execution of the optimizing compiler, aiming to eliminate the need for an interpreter 1.

We write Java methods that almost look like you're writing an interpreter in Java, and we compile these methods.

--- Doug Simon

This innovative design allows for efficient execution by compiling Java methods into machine code, indexed by bytecode opcodes 2.

   

Meta-Circular Design

Maxine's meta-circular design, where the VM is written in Java, enhances its development and operational efficiency. Doug Simon highlights that this design allows Maxine to optimize itself, setting it apart from other JVMs like HotSpot 3. The VM's architecture facilitates easy modifications, such as intercepting the JNI function interface, which is implemented as standard Java code. This flexibility supports experiments like software transactional memory and trace-based compilation, demonstrating Maxine's adaptability 4.

Our initial considerations of what you'd need to do that show that you only have to touch a few parts of Maxine VM to get a long way.

--- Doug Simon

Collaborations with institutions further explore Maxine's potential, showcasing its penetrability and ease of experimentation.