MoHCA-Java: a tool for C++ to Java conversion support
Proceedings of the 21st international conference on Software engineering
Cappuccino — A C++ to Java translator
SAC '98 Proceedings of the 1998 ACM symposium on Applied Computing
Java Native Interface: Programmer's Guide and Reference
Java Native Interface: Programmer's Guide and Reference
Strategies for Migration from C to Java
CSMR '01 Proceedings of the Fifth European Conference on Software Maintenance and Reengineering
Cibyl: an environment for language diversity on mobile devices
Proceedings of the 3rd international conference on Virtual execution environments
Implementing fast JVM interpreters using Java itself
Proceedings of the 5th international symposium on Principles and practice of programming in Java
Portable execution of legacy binaries on the Java virtual machine
Proceedings of the 6th international symposium on Principles and practice of programming in Java
WappenLite: a web application framework for lightweight programming environments
ITHET'10 Proceedings of the 9th international conference on Information technology based higher education and training
Hi-index | 0.00 |
Existing techniques for using code written in an unsafe language within a safe virtual machine generally involve transformations from one source code language (such as C, Pascal, or Fortran) to another (such as Java) which is then compiled into virtual machine bytecodes.We present an alternative approach which translate MIPS binaries produced by any compiler into safe virtual machine bytecodes. This approach offers four key advantages over existing techniques: it is language agnostic, it offers bug-for-bug compiler compatibility, requires no post-translation human intervention, and introduces no build process modifications.We also present NestedVM, an implementation of this technique, and discuss its application to six software packages: LINPACK (Fortran), which was used as one of our performance tests, TEX (Pascal), which was used to typeset this document, libjpeg, libmspack, and FreeType (all C source), which are currently in production use as part of the Ibex Project [13], and gcc, which was used to compile all of the aforementioned.Performance measurements indicate a best case performance within 3x of native code and worst case typically within 10x, making it an attractive solution for code which is not performance-critical.