Jikes RVM Home
Jikes RVM (Research Virtual Machine) provides a flexible open testbed to prototype virtual machine technologies and experiment with a large variety of design alternatives. The system is licensed under an OSI approved license. Jikes RVM runs on many platforms and advances the state-of-the-art of virtual machine technologies for dynamic compilation, adaptive optimization, garbage collection, thread scheduling, and synchronization. A distinguishing characteristic of Jikes RVM is that it is implemented in the Java™ programming language and is self-hosted i.e., its Java code runs on itself without requiring a second virtual machine. Most other virtual machines for the Java platform are written in native code (typically, C or C++). A Java implementation provides ease of portability, and a seamless integration of virtual machine and application resources such as objects, threads, and operating-system interfaces.
Many researchers have found that Jikes RVM provides a useful vehicle for research on the frontiers of virtual machine technologies (over 188 publications and 36 dissertations), as well as teaching courses. If you are looking for where to start reading about Jikes RVM we have a recommended reading page.
Recent Jikes RVM Project News
Jikes RVM 3.1.4 Released (18 February 2016)
Jikes RVM version 3.1.4 has been released and is available for download at https://github.com/JikesRVM/JikesRVM/archive/3.1.4.tar.gz.
Highlights of the release can be found in the release notes.
Migration of source code repositories to GitHub (15 September 2015)
The previous workflow for code contributions remains unchanged. In addition to this, we will accept pull requests on GitHub for now. However, we reserve the right to change our minds if we don’t like the pull request workflow.
Mirroring of historical Subversion repositories on GitHub, possible move of current Mercurial repositories to GitHub (06 September 2015)
We plan to mirror parts of our historical Subversion repository on GitHub. In order to do a proper conversion from Subversion to Git, Subversion author names must be mapped to name-email pairs. An initial set of mappings is available at the bottom of the Source Control page. If you notice errors or omissions, feel free to send us changes or pull requests for the website sources.
Additionally, we’re considering a move of our main repositories to GitHub. This is being discussed on the core mailing list.