dynarmic VS libmorton

They're probably referring to dynarmic: https://github.com/merryhime/dynarmic

As an HLE, touchHLE is radically different from a low-level emulator (LLE) like QEMU. The only code the emulated CPU executes is the app binary and a handful of libraries; touchHLE takes the place of iPhone OS and provides its own implementations of the system frameworks (Foundation, UIKit, OpenGL ES, OpenAL, etc).

https://github.com/merryhime/dynarmic/pull/697 - Dynarmic implementing Arm backend support. Dynarmic is a dynamic recompiler for ARM.

I did some work on Dynarmic, so there's my bias I guess. But I def believe Dynarmic would emit better context-aware assembly than a CIL->Native jitteror the JVM would emit. Dynarmic takes advantage of instruction sets like BMI2 and AVX{2,512} and uses a pretty darn concise intermediate representation to the original ARM assembly to emit efficient x86 while a C# JIT probably still only emits baseline x86-64 and struggles with efficient vectorization of things like Arm's NEON instructions. Can't even imagine a C# or Java VM trying to automatically emit optimal assembly for an FMADD including handling NaN propagation or detecting that FMINNM can be very quickly emulated with a single vrangep{s,d} x86 instruction.

For emulators, it's currently used in dynarmic(Yuzu's ARM-to-x86 recompiler backend) for the fast emulation of ARM's NEON instruction set.

3. https://github.com/Forceflow/libmorton

I used it to accelerate nearest neighbor detection for collision processing in particle-laden flow for modeling complicated domains in 3d (for biological fluids simulation). I was using it a locality sensitive hashing to put particles near each other in the same bucket in an hash map. I came across the ideas of BIGMIN (big minimum) and LITMAX (little maximum) for range search in a morton encoded data that I found to be cool.

For example, I was able to accelerate ARM's vector-based arithmetic/logical bit-shifts into a single instruction compared to the 5 instructions it needed before thanks to AVX-512(also here's a little writeup I made on that). Or how I was able to accelerate ARM's vector bit-reversal into a just 2 fast instructions rather than the dozen that it needed before(another write-up I made on that). Or how using AVX512-BITALG can help accelerate interfacing with Morton Codes(common with encoding and decoding GPU texture formats).