This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages) (Learn how and when to remove this message)
|
| Maxine | |
|---|---|
| Original authors | Bernd Mathiske, Douglas Simon (Sun Labs,Oracle) |
| Developers | University of Manchester, Maxine team |
| Initial release | 2005; 21 years ago (2005) |
| Stable release | |
| Written in | Java |
| Operating system | Solaris,Linux,macOS |
| Platform | x64, ARM32, AArch64, RISC-V |
| Type | Java virtual machine |
| License | GPL version 2.0 |
| Website | github |
| Repository | |
TheMaxine virtual machine is an open sourcevirtual machine that is developed at the University of Manchester.[2] It was formerly developed bySun Microsystems Laboratories,[3] since renamed Oracle Labs. The emphasis in Maxine'ssoftware architecture is on modular design and code reuse for flexibility, configurability, and productivity for industrial and academic virtual machine researchers. It is one of a growing number ofJava virtual machines written entirely in Java in ameta-circular style. Examples includeSquawk andJikes RVM.
The Maxine VM is characterized internally by aggressive use of advanced language features in Java 1.5 and 1.6, by modular subsystems coordinated through Java interfaces, by the absence of aninterpreter, and by a tightly coupled debugger and visualizationtool for VM development.
Maxine isplug compatible with an unmodifiedJava Development Kit (JDK). Maxine can be developed, built, and run in standard Javaintegrated development environments (IDEs), includingNetBeans,Eclipse, andIntelliJ IDEA.
A secondary goal of the project is to develop methods and tools for "systems programming in Java".Compiler extensions, configured in VMsource code usingJava annotations, allow use, with no performance penalty, of low-level operations otherwise disallowed in Java. These extensions provided the foundation for theGraal compiler.
Specialized debugging support for the Maxine VM is provided by the Maxine Inspector: a companion tool that acts as a combined object, class, and method browser, and as a machine- and bytecode-level debugger.[4]The Inspector runs out-of-process, needs no active VM support, and leverages code shared with the VM for specialized developer services that exploit detailed knowledge of memory layout and VM design.[5]Notable services include:
Maxine was created by Bernd Mathiske at Sun Labs in early 2005. He led its development among a growing team until late 2008 when he leftSun Microsystems and handed the project over to Doug Simon who had been the first engineer to join it. Doug Simon continued in this role throughout the acquisition of Sun byOracle Corporation.
The static (heap inspection) version of the Maxine Inspector was created by Bernd Mathiske in 2006. Michael Van De Vanter assumed development of the Inspector in 2007, adding dynamic support as the VM became executable and continued to evolve throughout the acquisition of Sun byOracle Corporation.
Oracle continued development of Maxine until the release of Maxine 2.0.[16] The University of Manchester is developing Maxine as of release 2.1.[17]
{{cite web}}: CS1 maint: archived copy as title (link)