![]() Then we detail how we handle allocations from the combiner interpreter using a stack object (dual stack) allocated in the heap and avoid allocations done by the continuation mechanism.Īt the end, we present a comparison of the execution time with and without the allocation minimization. First we explain how we avoid allocations from the C interpreter using a stack frame allocation (fake stack frame). This paper describes how we minimize the allocation done by our implementation of the JSR 292 on Android. The implementation presented in is slowed down by several allocations done by the C interpreter and the combiner interpreter. Dalvik which uses a C interpreter for direct method handles and a Java flexible interpreter for the "combiner" method handles. Android 292 is our implementation of the JSR 292 on top of. Android, the Google operating system for embedded devices, uses for its applicative part a Java-based virtual machine called Dalvik. To improve and simplify the implementation of dynamically typed languages on top of the Java virtual machine, Java 7 introduced a new instructions set as well as a new API specified by the JSR 292. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |