Ok, so it's AOT.. but this is their own backend? (not the LLVM one?) and will have no JIT at all? If they troubled creating their own IR and are not reusing t

Ok, so it's AOT.. but this is their own backend? (not the LLVM one?) and will have no JIT at all? If they troubled creating their own IR and are not reusing the LLVM one.. it probably means that the LLVM backend are only being used to retarget to the several architectures supported by it.. Otherwise it doesnt make much sense, since they are controlling the optimizing compiler in a custom way without the LLVM help in that matter Also, if we remember they use renderscript targeting the LLVM and, that the output could go directly to the graphic processors instead of the cpu, it make more sense to have this sort of design.. They work directly in the ABI and voila, everything just works and talk to each other despite its different roots (java, ndk, renderscript.. + ..put something else here..)