article · 2008
An annotation-aware java virtual machine implementation. Concurrency - Practice and Experience
Ana Azevedo, Alex Nicolau, Joe Hummel
Cited by 0Abstract and details only
Abstract
The Java bytecode language lacks expressiveness for traditional compiler optimizations, making this portable, secure software distribution format ine cient as a program representation for high performance. This ine ciency results from the underlying stack model, as well as the fact that many bytecode oper-ations intrinsically include sub-operations (e.g., iaload includes the address computation, array bounds checks and the actual load of the array element). The stack model, with no operand registers and limiting access to the top of the stack, prevents the reuse of values and bytecode reordering. In addition, the language has no mechanism to indicate which sub-operations in the Java bytecode stream are redundant or subsumed by previous ones. As a consequence, the Java bytecode language inhibits the expression of important compiler optimizations, including register allocation and instruction scheduling. The Java bytecode stream generated by aJava bytecode compiler is a signi cantly under-optimized program representation. The most common solution to overcome this ine ciency is the use of a Just-in-Time (JIT) compiler to not only generate native code, but perform optimization as well. However, the latter is a time consuming operation in an already time-constrained translation process. In this paper we present an alternative to an optimizing JIT compiler that makes use of code annotations generated by aJava bytecode compiler. These annotations carry information concerning compiler optimizations. During the translation process, an annotation-aware Java Virtual Machine (JVM) system then uses this information to produce high performance native code without performing much of the necessary analyses or transformations. We describe the implementation of a prototype of an annotation-aware JVM consisting of an annotation-aware JIT compilation system. We conclude the paper showing performance results comparing our system with other JVMs running on SPARC architecture. 1
Cite this paper
Azevedo, A., Nicolau, A., & Hummel, J. (2008). An annotation-aware java virtual machine implementation. Concurrency - Practice and Experience.
Azevedo, Ana, et al. “An annotation-aware java virtual machine implementation. Concurrency - Practice and Experience.” 2008.
Azevedo, Ana, Alex Nicolau, and Joe Hummel. 2008. “An annotation-aware java virtual machine implementation. Concurrency - Practice and Experience.”
Azevedo, A., Nicolau, A. and Hummel, J. (2008) ‘An annotation-aware java virtual machine implementation. Concurrency - Practice and Experience’.
@article{azevedo2008annotation,
title = {{An annotation-aware java virtual machine implementation. Concurrency - Practice and Experience}},
author = {Azevedo, Ana and Nicolau, Alex and Hummel, Joe},
year = {2008}
}Made from the index record. Check names, capitalisation and page numbers against the paper. Need another style? AI for Research has over 10,000.