3 ms·
It was kind of a half baked idea. At best, it could lower the small overhead of the interpreter loop for a subset of Java bytecodes. At some point you’d need a
by gok 9y ago
It was kind of a half baked idea. At best, it could lower the small overhead of the interpreter loop for a subset of Java bytecodes. At some point you’d need a JIT to get better performance, and that JIT would want to target real ARM code (so you can do things like register allocation)
One cool thing about Java on little processors is that you can get memory safety without an MMU. But again at some point you’re going to want an MMU anyway...
- pjmlp 9y agoThat is the whole premises of language OSes, type safety over MMU. But it is as you say, given enough memory to manage or the usual performance tricks for GC/JIT, and the MMU will be needed.