| ▲ | pjmlp 3 days ago | |
Meanwhile Oracle has been doing it since 2015 with SPARC ADI on Solaris. I do agree it is a pain not seeing this becoming widely adopted. As for disabling JIT, it would have the same effect as early Androids, lagging behind Symbian devices, with applications that were wrappers around NDK code. | ||
| ▲ | ignoramous 2 days ago | parent [-] | |
> As for disabling JIT, it would have the same effect as early Androids DVM tried to mitigate the slowness with JIT+SSA, but ART mixed in JIT+SSA alongside AOT+PGO (that is, a no JITing ART means a full AOT ART, unlike in DVM where the Interp takes over when in vmSafeMode). Even if the runtime will continue to lag in terms of power/performance efficiency wrt ObjC/Swift, Google should at least let the developers decide if they want to disallow JIT from creating executable memory regions inside their app's sandbox, like Apple does: https://developer.apple.com/documentation/security/hardened-... | ||