Add ARMV8L support for low-end phones.

11-05-2018, 08:56 AM #1

ARMV7x is old but what about ARMV8L? If you can develop this ARMV8l arch. Ok, my phone haves Armv8l based SoC. But sadly armv8l is not supported on Dolphin Emulator. Thanks.

**JosJuice** · 11-05-2018, 09:09 AM #2

Dolphin actually only supports ARMv8 right now. (Or well, it does support x86-64 too, but the point is that it doesn't support ARMv7.)

**mbc07** · 11-05-2018, 09:15 AM #3

I've never heard of ARMv8L before and a quick Google search didn't yield any conclusive insight. What I can say is that given the flagship devices of nowadays still struggle with most games in the Android port of Dolphin, it's very unlikely to expect support for this ARMv8L architecture in near future, especially if it requires coding a new JIT and if it's restricted to low-end phones...

11-05-2018, 09:22 AM #4

I have shared my ideas. But armv8l usually comes out on low phones. The only remedy is either a custom kernel or a new device. But you need an ARMV8A based custom kernel. Very big thanks.

**Helios** · 11-05-2018, 09:30 AM #5

It's ARMv8 running in 32 bit mode.

Anyways the answer is probably no. We have nobody interested in writing a JIT for ARMv8 in 32-bit mode and even if we did we've been burned by merging in complex masses of code with one person to maintain it.

So this probably won't happen, sorry.

**degasus** · 11-05-2018, 05:47 PM #6

Please use the correct names for this: AARCH64 and AARCH32. The former is the 64bit instruction set, the latter is the 32 bit instruction set. We only support AARCH64 and we will not support AARCH32.

ARMv8 and ARMv7 are plattforms. The former supports both AARCH64 and AARCH32, that is the way how you can still start 32 bit applications on your recent mobiles. ARMv7 however is the very dated plattform which only supports AARCH32.

We provide a Just In Time Compiler for fast execution. But this needs to be rewritten per *Instruction Set*. We don't care about the plattform at all, we aren't an operating system.

11-05-2018, 07:08 PM #7

What's with the ARMv7a? I'm telling you once. You don't want to do it. There's nothing wrong with this Emulator. It's not just 32-bit architecture. You can't fool anybody. As an example we have 5.0 RC armv7 ~ armv8l support. If it's an architecture, you're promoted to it. Programming can't be like that. Think of an Intel Atom Z3735x device. Imagine that the x86 architecture exists and runs with the unstable Operating System. You say you use with Dolphin 4.0. This is an injustice.

**JosJuice** · 11-05-2018, 07:17 PM #8

(11-05-2018, 07:08 PM)CyberSaturn Wrote: What's with the ARMV7a? I'm telling you once. You don't want to do it.

That's right. None of us see any reason to do it, because devices that don't support 64-bit code wouldn't be able to run Dolphin fast enough even if we wrote a JIT for them.

**degasus** · 11-05-2018, 07:28 PM #9

(11-05-2018, 07:08 PM)CyberSaturn Wrote: You say you use with Dolphin 4.0. This is an injustice.

Oh no. Please don't use 4.0 on this device. Write your own emulator for this device. Welcome to voluntary driven projects. Do whatever you want to do, but don't expect us to care about you!

11-05-2018, 09:29 PM **#10**

(11-05-2018, 07:28 PM)degasus Wrote: Oh no. Please don't use 4.0 on this device. Write your own emulator for this device. Welcome to voluntary driven projects. Do whatever you want to do, but don't expect us to care about you!

Good idea, JIT Recompiler Armv8 (32 bit) decided to develop. It's a good idea to try and make sense. Smile

I'm closing the thread. Thanks.