I know very very basic about programming, if I may ask: is it too hard to make an "arm32" functional build? (without JIT support, this would require a port) Just curiousity.
(10-18-2018, 04:46 AM)Guilherme Wrote: [ -> ]Cool! This must be as slow as early versions when we had 32-bit support. I tested old builds before, but I haven't seen many games booting here, I wonder if at least the "compatibility" has improved.
With the old 32bit PC / Linux build (4.0.2) the compatibility is less and there are several problems with textures and sound.
https://en.m.wikipedia.org/wiki/Just-in-time_compilation
There was also a 32bit version of the pre-alpha stage for Android but was immediately shelved, in favor of 64Bit.
Android uses a virtual machine written in Java, if this is what you want to know, and the only way to get performance with any emulator with important resources on this platform (example, Dolphin and a ppsspp, or Reicast), is to enable the JIT compiler.
At the moment, as far as I know, the only emulator using a compiler other than JIT is Yaba Sanshiro (fork, Not Opensource or semi OpenSource, of the original Yabause Project), with the LLVM:
https://en.m.wikipedia.org/wiki/LLVM
but it does not have the same versatility as a JIT compiler, it is compatible but requires more study and attention and is not very popular at the moment.
PS: The author is also thinking of moving to 64Bit;
http://www.uoyabause.org/blogs/51
The 32Bit, now they are prehistory.
(10-18-2018, 04:46 AM)Guilherme Wrote: [ -> ]Cool! This must be as slow as early versions when we had 32-bit support. I tested old builds before, but I haven't seen many games booting here, I wonder if at least the "compatibility" has improved.
A modern 32-bit build should have about as good compatibility as a modern 64-bit build (though maybe some games will get upset at the slow speed if you don't disable dual core).
(10-18-2018, 06:59 AM)JosJuice Wrote: [ -> ]A modern 32-bit build should have about as good compatibility as a modern 64-bit build (though maybe some games will get upset at the slow speed if you don't disable dual core).
It should have an as good compatibility as a modern 64-bit DESKTOP build. It uses the interpreter which is shared with the desktop
(10-18-2018, 07:08 AM)degasus Wrote: [ -> ]It should have an as good compatibility as a modern 64-bit DESKTOP build. It uses the interpreter which is shared with the desktop
Yes, assuming the interpreter doesn't have any bugs when compared to the x64 JIT, which is likely but not guaranteed
The problem, according to my point of view, is with the SoC Mediatek, many are still at 32Bit.
Or, in the case of TVBoxes, they still have Android versions running at 32Bit, despite the SoC, allow 64Bit.
The problem is Mediatek.
(10-18-2018, 07:19 AM)stizzo Wrote: [ -> ]The problem, according to my point of view, is with the SoC Meadiatek, many are still at 32Bit.
Or, in the case of TVBoxes, they still have Android versions running at 32Bit, despite the SoC, allow 64Bit.
The problem is Mediatek.
And many of them don't support OpenGL ES 3
Yep!
Mediatek, are also very used by crackers, to create malware to pre-install or to infect the kernel that the mediatek created and closed.
This on every mediatek machine.
PS: from my point of view, the best SoC to work on is Qualcomm Snapdragon, followed by Exynos and Kirin.
The rest is rubbish.