Does your library behave the same on ARM64 as on x86?
Build your tests twice, run both, and diff the output. Ounce-Core runs the ARM64 build on three engines and shows the first line that differs, so you can reproduce and report an ARM64 problem without owning ARM hardware. It has found real bugs this way, in the emulator itself, using libraries like yours.
Follow the guide Suggest your library1. Write one test
A small C file that exercises your library and prints deterministic text. The same file builds for your computer and for ARM64.
2. Run both
The host build is the reference. The ARM64 build runs in Ounce-Core on the interpreter, the JIT and native execution.
3. Diff
Identical output is retained as evidence. A difference points at an instruction or a line, with a small reproduction to share.
What it can and cannot tell you
It can show that your tests behave identically on the engines for the inputs you wrote, and help you reproduce a failure someone reports on ARM64.
It cannot run your whole application, replace testing on real ARM64 hardware, or prove your library correct. It is not fast, and many instructions are still undecoded; an unsupported instruction stops the run with its opcode so the gap is visible, not silent. Running arbitrary Linux applications is not established.
Not sure it fits? Look at the results for LZ4, xxHash, SQLite, Lua and others, then ask in Discussions.