On Armv8 CPU's I think it would be a good idea to allow users to choose whether to engage the 64 bit JIT. Since it is less mature it may be more productive on the user side to use 32bit. At least until the 64bit JIT is comprehensively better.
Option for AArch32 and AArch64
|
09-28-2014, 12:16 PM
If Android's JNI routine allows it then it shouldn't be too much of an issue.
It'll have to be investigated once I get a AArch64 device. Hopefully by time one becomes available the missing instructions in the AArch64 JIT won't really be an issue and it'll still be quick. 09-29-2014, 04:28 AM
(09-28-2014, 12:16 PM)Sonicadvance1 Wrote: If Android's JNI routine allows it then it shouldn't be too much of an issue.I believe JNI allows it for the sake of backwards compatibility (i.e ARMv8 devices compile 64 bit Java code, but the C code may still be 32 bit, so they support interchangeable C code from my knowledge. They mentioned it briefly on one of the Google IO bytes regarding ART and 64 bit.) 09-29-2014, 10:39 AM
Your right on that count.
The issue is when shipping both a ARMv-7 and AArch64 JNI library in the binary we will have to move away from using Androids automatic architecture detection and choose which one we want instead. It'll have to be something I test. 09-29-2014, 12:04 PM
(09-29-2014, 10:39 AM)Sonicadvance1 Wrote: Your right on that count.Could it be possible to distribute seperate builds the way desktop dolphin did it? Not sure because it would complicate any future play store releases. 09-29-2014, 01:07 PM
Shouldn't be needed due to subverting automatic detection is relatively painless.
Again speculation, we'll have to wait a few months to know for sure. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)