Not only that, but it's also good to note that Android != Java. It's best described as Java-like, in that there are some libraries/features in Java that aren't supported in Android, so it's a bit of a misnomer to describe it as a full JVM.
I think the only difference might be the portability. Android takes 'Java' code and outputs 'android machine code' that can/does only runs on an 'android machine' (I think).
Compiled Java in theory should run the same on any JVM, as it's virtual machine code, and the 'machines' use the same set of defined instructions.
For example, J9, http://www-01.ibm.com/software/wireless/wece/features.html
==> jar2jxe: A utility for converting Java class and archive files to the native J9 JXE file format.
Or JamaicaVM Builder
https://www.aicas.com/cms/sites/default/files/jamaicavm_6.3_...
The big difference between these JVM and Dalvik, is that they are certified JVMs, whereas Google tried to workaround the licensing issue for embedded Java deployments.
It depends on which JVM you talk about.
IBM J9 does it if I am not mistaken.
Additionally, the OS/400 JVM is integrated with the kernel JIT used for the bytecode executable format of OS/400 applications (TIMI)
http://www.drdobbs.com/new-to-the-as400/184404408
> I think the 3 sweet-spots are:
A few more to your list. These do all three.
- IBM Websphere RealTime J9
- Aonix Perc
- JamaicaVM
- Excelsior JET
Sometimes I find a bit sad that many equate JVM == OpenJDK, not understanding how many choices are out there.