box64

box64: https://github.com/ptitSeb/box64

There is Box86/box64/box32. A bit confusing but it's box86 for x86 > ARM32. Box64 for x86_64 > ARM64. And Box32 for x86 > ARM64. I think they mention games because a lot of other software for Linux is generally open source. So a lot of times it's pretty easy to get an ARM build. It also does a neat performance trick where it intercepts library calls and redirects them to native versions of the same library. http://github.com/ptitSeb/box64

The felix86 compatibility list also lists SuperTux and SuperTuxCart. "lsteamclient: Add support for ARM64." https://github.com/ValveSoftware/Proton/commit/8ff40aad6ef00... .. https://news.ycombinator.com/item?id=43847860 /? box86: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... "New box86 v0.3.2 and Box64 v0.2.4 released – RISC-V and WoW64 support" (2023) https://news.ycombinator.com/item?id=37197074 /? box64 is:pr RISC-V is:closed: https://github.com/ptitSeb/box64/pulls?q=is%3Apr+risc-v+is%3...

Wine doesn't do any of that as far as I know. It loads a Windows PE file, it's (placeholder) DLL dependencies, and starts executing at the main entrypoint. Box64 does translation and has some specific placeholder DLLs that intercept API calls and call native code rather than emulating the entire process. If what you describe is being done, it's being done by Box64. I don't know enough about aarch64 to know what ARM64X and ARM64EC do, though. I can find [a Github comment](https://github.com/ptitSeb/box64/pull/858#issuecomment-16057...) where one of the authors states that the goal is to implement ARM64EC, but I wouldn't know what the status is on that.

Box64 only does 64-bit binary translations. So for example Steam cannot run on box64 alone because it's a hybrid with both 32-bit and 64-bit binaries: https://github.com/ptitSeb/box64/?tab=readme-ov-file#notes-a... Wine has beta support for 32-bit Windows applications on 64-bit-only wine, but it's not default. They also address it: https://docs.fedoraproject.org/en-US/fedora-asahi-remix/x86-...

Author here, we have adopted this approach as a fast path to box64: https://github.com/ptitSeb/box64/pull/1763, thank you very much!

> Wine can also be compiled/run as native. I'm not sure you can run Wine natively to run x86 Windows programs on RISC-V because Wine is not an emulator. There is an ARM port of Wine, but that can only run Windows ARM programs, not x86. Instead box64 is running the x86_64 Wine https://github.com/ptitSeb/box64/blob/main/docs/X64WINE.md

macOS runs x64 executables just fine through Rosetta so I don't see why Wine couldn't make use of that hardware acceleration. It's also possible to only simulate the entrypoints through Rosetta and then execute native aarch64 code from there. On Linux https://github.com/ptitSeb/box64 does exactly that, for example. However, with the performance Apple has been able to squeeze out of Rosetta, I'm not sure of that workaround is even necessary.

You could have a look at box86 and box64: https://box86.org/ | https://github.com/ptitSeb/box64 I haven't tried them myself, but I've read consistent testimony that the performance (and compatibility) is great.

https://github.com/ptitSeb/box64 can do it a little lighter than a full qemu VM

> PtitSeb [creator of Box86 and Box64 projects]: My main goal was to create an x86 emulator that ran on low-spec hardware [...] I wanted a small and fast emulator for my [ARM] Open Pandora [...] My goals were to have something that was fast and easy to use ... [while] the main goal of QEMU is to be as precise and as close to the real hardware as possible[, I accept] some approximation [for speed] Link to Box64: https://github.com/ptitSeb/box64 Benchmarks seem to reveal a performance of 85% the original.

Until last week, I had a full Debian amd64 systemd container to run invidious on an ARM64 machine (a ROCKpro64) running Armbian, since crystal (the language in which Invidious is written) does not have arm64 Debian packages. There's nothing special to make this work, regular commands work, for instance just running systemd-nspawn -b in an arm64 root folder works. Now I found a way to get arm64 crystal binaries. I got rid of the container, but Invidious still cross compiles to amd64, so qemu is still used to run an amd64 build Invidious of transparently. binfmt and qemu-user do wonders. It works well. One could use box64 [1] instead of qemu and it should provide better performance because it uses the native versions of some well known libraries (including libc6) instead of emulating them, but I failed to compile box64 this weekend so I sta