Effectiveness of cross-platform optimizations for a java just-in-time compiler
Effectiveness of cross-platform optimizations for a java just-in-time compiler
复制标题
java 即时编译器跨平台优化的有效性
DOI：
10.1145/949305.949322
复制
发表时间：
2003
期刊：
影响因子：
--
通讯作者：
T. Nakatani
中科院分区：
文献类型：
--
作者：
K. Ishizaki;Mikio Takeuchi;K. Kawachiya;T. Suganuma;Osamu Gohda;T. Inagaki;A. Koseki;Kazunori Ogata;M. Kawahito;T. Yasue;T. Ogasawara;Tamiya Onodera;H. Komatsu;T. Nakatani
本文介绍了我们Java Just-Indime（JIT）编译器的系统概述，该编译器是IBM Java JIT编译器最新生产版本的基础，该编译器支持多样化的处理器架构，包括32位和64位模式，CISC，RISC和VLIW架构。特别是，我们专注于在不同体系结构中常见的跨平台优化的设计和评估。我们通过在三个不同的平台上选择性地将其在JIT编译器中选择性地禁用：IA-32，IA-64和PowerPC通过选择性禁用了每个优化的有效性。我们的详细测量使我们能够根据最小的汇编时间的最大性能改进来对优化进行排名。已确定的集合包括仅用于微小方法的方法，使用前向数据流分析和部分冗余消除的例外检查消除，例如使用数据流分析的标量替换和类字段，用于类型包含检查的优化以及消除控制流中的合并点图。与使用所有优化相比，这些优化可以实现这些平台上两个行业标准标准基准计划的90％的峰值性能，仅34％的编译时间。
This paper describes the system overview of our Java Just-In-Time (JIT) compiler, which is the basis for the latest production version of IBM Java JIT compiler that supports a diversity of processor architectures including both 32-bit and 64-bit modes, CISC, RISC, and VLIW architectures. In particular, we focus on the design and evaluation of the cross-platform optimizations that are common across different architectures. We studied the effectiveness of each optimization by selectively disabling it in our JIT compiler on three different platforms: IA-32, IA-64, and PowerPC. Our detailed measurements allowed us to rank the optimizations in terms of the greatest performance improvements with the smallest compilation times. The identified set includes method inlining only for tiny methods, exception check eliminations using forward dataflow analysis and partial redundancy elimination, scalar replacement for instance and class fields using dataflow analysis, optimizations for type inclusion checks, and the elimination of merge points in the control flow graphs. These optimizations can achieve 90% of the peak performance for two industry-standard benchmark programs on these platforms with only 34% of the compilation time compared to the case for using all of the optimizations.