PPSA26344 · module eboot

Ghost of Yotei — matching decompilation

Source code that, compiled with the original toolchain, reproduces the shipped binary byte for byte. This page shows only what the repository can prove: the binary itself is never in it, and every figure is recomputed from committed data by make report, which the commit gate re-runs and compares.

Progress

Three measurements, not three stages. They move independently — matching does not require readable code, and readable code is not verified code.

No inventory yet. The denominator comes from the compiler’s own unwind table in the shipped binary, and that dump has not landed. Until it does these read zero of zero, which is the honest number rather than a placeholder.

Matched

0 / 0 functions

The C compiles to the shipped bytes, verified against the binary.

Converted

0 / 0 files

Readable without the binary open beside you. Five criteria, all required.

Validated

0 / 0 matched functions

Matched code that behaves, checked against emulation or hardware.

Table view
TierDoneTotalPercent
Matched00
Converted00
Validated00

How close the unmatched work is

Distance is diverging instructions from the shipped bytes. An attempt four instructions off is nearly-correct C, not a failure, so every one is kept — 0 banked, 0 within eight and retryable, 0 floored as compiler-internal.

Nothing banked yet. Attempts land here the first time bytematch.py runs against a real target.

Toolchains

A match claim is only true of the compiler that earned it, so each is pinned by the SHA-256 of its driver binary. None is marked canonical: which one built the game is settled by measurement, not preference.

ToolchainVersionPinState
apple-17.0.0Apple clang version 17.0.0 (clang-1700.0.13.5)bed335fb48472e4epinned
llvm-20.1.8Homebrew clang version 20.1.8c6ce2e418d70299epinned
llvm-22.1.8Homebrew clang version 22.1.8adc60242d6106c7fpinned

How to read this

Percentages are computed from committed data only; the binary is never in this repository.

Every matched row records the SHA-256 of the target bytes it was aimed at, so any holder of the same dump can reproduce the claim.

MATCHED, CONVERTED and VALIDATED move independently; matching does not require readable code and readable code is not verified code.