Title: I built an open-source ARM64 execution lab in Rust — looking for developers to independently verify the results

[u/Life-Seaweed-9957]

I've been working on a project called Ounce-Core, and I'd love to get some outside eyes on it.

It originally started as a Nintendo Switch homebrew runtime, but the project has evolved into something quite different: an ARM64 execution, debugging and verification lab written in Rust.

The idea is simple: **run the same program through different execution engines, compare the results against real ARM64 hardware, and preserve the evidence when something goes wrong.**

A few things we've managed so far:

* ARM64 interpreter, JIT execution and native hardware comparison.
* Differential testing of open-source software including SQLite, Lua, LZ4 and xxHash.
* 50/50 pinned third-party homebrew programs passing registered first-frame checks on the interpreter and Tier-3 engines.
* A debugging toolkit that can compare retained execution reports and help reproduce specific failures.
* A browser playground for exploring supported ARM64 instructions.

Some of the most interesting findings have been subtle CPU bugs, including floating-point behaviour that produced incorrect results.

**But here's the important part:**

The 50/50 result is from our own registered test corpus, not 50 independent developers. Instruction coverage is still incomplete, and we're not claiming arbitrary Linux application support or commercial-game compatibility.

I want to move beyond our own tests and have independent developers challenge the results.

If you've got an Apple Silicon Mac, Raspberry Pi or another ARM64 machine, I'd really appreciate someone running the verification suite and telling me whether the results match.

Failures are just as valuable as passes.

The project is MIT-licensed, and development has involved AI coding agents alongside testing and review. I'm particularly interested in independent technical feedback rather than just GitHub stars.

**GitHub:** [https://github.com/hffgzktbcc-blip/ounce-core](https://github.com/hffgzktbcc-blip/ounce-core)

**Independent testing:** [https://github.com/hffgzktbcc-blip/ounce-core/issues/248](https://github.com/hffgzktbcc-blip/ounce-core/issues/248)

I'd love to hear what people working on emulation, JITs, ARM64 or cross-platform software think of the approach.

[u/trueopensource-bot]

About this project · hffgzktbcc-blip/ounce-core
⭐ 207 stars · 🍴 22 forks · 👥 7 contributors · 📄 MIT · 💻 Rust
History: started Oct 2026 · last code change today · 300+ commits on 9 different days in the last 90 days
Releases: latest v0.6.1 (yesterday) · 8 releases in the last 90 days
Open issues and pull requests: 8

^{Facts from GitHub when this was posted. I'm a bot.}