4 ms·
This is wonderful news, but Graal is sadly behind the times there. Android had AOT compilation of Java bytecode (well, technically Dalvik bytecode) since 2013.
by yc12340 6y ago
This is wonderful news, but Graal is sadly behind the times there.
Android had AOT compilation of Java bytecode (well, technically Dalvik bytecode) since 2013. It was upgraded to hybrid AOT/JIT mode in 2016. All of it was open-sourced, unlike Graal, where many key optimizations (such as auto-vectorization) remained proprietary.
Unlike GraalVM's AOT mode, Android VM can run existing Java libraries without any code changes — you don't have to painstakingly look for static variables and mark them for late loading, and reflection just works.
- suyash 6y agoIf you're comparing Android with Graal, you don't understand what Graal is all about.
- pjmlp 6y agoYou are the one behind the times, Java has had support for AOT compilation since around 2000, just not as free beer. Most 3rd party commercial JDKs have offered it, specially for embedded deployment scenarios. Besides Android Java isn't Java, rather a Google dialect with cherry picked packages from (nowadays) OpenJDK, most likely to die frozen in its current state as they embrace Kotlin über alles.
- kaba0 6y agoAOT is not by itself anything good/fancy. As others mentioned, java could be AOT compiled since ancient times. Graal is state of the art/interesting, because it uses a different compilation technique than usual, looking at the program to be compiled incorporated with the interpreter for that compilation - which result in superior results for AOT compilation, and in the case of a replacement of JIT compilers, it looks promising (but not yet surpassing Hotspot). Android’s java is pretty terrible in comparison, just saying.
- deleted 6y ago[deleted]