jacobin

A more-than-minimal JVM written in Go.

Status

Intended feature set:

• Runs Java 21 classes, but...
• No JNI (Oracle intends to replace it; see JEP 389)
• No security manager (Oracle intends to remove it; see JEP 411)
• No JIT
• Somewhat less stringent bytecode verification
• Does not enforce sealed classes

What we've done so far and what we need to do:

Command-line parsing

• Gets options from the three environment variables. Details here
• Parses the command line; identify JVM options and application options
• Responds to most options listed in the java -help output

To do:

• Handling @files (which contain command-line options)
• Parsing complex classpaths

Class loading

• Correctly reads and parses most classes
• Extracts bytecode and parameters needed for execution
• Automated pre-loading of core Java classes (Object, etc.)
• java.*, javax.*, jdk.*, sun.* classes are loaded from the JAVA_HOME directory (i.e., from JDK binaries)
• Handles JAR files
• Handles interfaces

To do:

• Handle more-complex classes (called via method handles, etc.)
• Handle inner classes

Verification, Linking, Preparation, Initialization

• Performs format check of class file.
• Performs preparation of a loaded class file.
• Linking and initialization -- minimally and only as needed at execution time

To do:

• Verification
• Robust linking and initialization

Execution

• Executes all bytecodes except INVOKEDYNAMIC, including one- and multi-dimensional arrays
• Static initialization blocks
• Throwing and catching exceptions
• Running native functions (written in go). Details here.

To do:

• Method handles
• Calls to superclasses
• Inner and nested classes
• invokedynamic bytecode
• Annotations

Instrumentation

• Class-loading instrumentation (use -trace=cloadi)
• Instruction-level tracing (use -trace=inst for a listing of class/method/instructions/size-of-op-stack for all instructions as they execute)
• Detailed instruction tracing (use trace=verbose to show everything in -trace=inst, plus the contents of the op stack for each instruction)

To do:

• Emit instrumented data to a port, for reading/display by a separate program.
• Write a UI component to watch the bytecodes executing and the changes in the various stacks

Garbage Collection

GC is handled by the golang runtime, which has its own GC

Understanding the Code

A detailed roadmap to the code base can be found in the wiki.

If you want to test Jacobin

At present, we're not looking for testers because we know the missing features and we're working on them. Testing, at this point, will likely result in frustration. However, if for your own enjoyment, you still want to try it out, see directions and cautions on our Release Page. (If you want some fun, run your program on Jacobin with the -trace:inst option and watch the executing Java bytecodes whiz by along with the changing contents of the operand stack.)

We expect/hope/trust that by the end of this year, we'll be ready to ask interested users to test Jacobin on real programs and share their feedback with us.

Thanks

The project's home page carries a lengthy note at the bottom that expresses our thanks to vendors and programmers who have made the Jacobin project possible. They are many and we are deeply grateful to them.