The matching loop
Pick a function, draft C, compile, diff, repeat. Read the workflow.
From first function to 100%
A practical guide to starting, and finishing, a matching decompilation. Written by people who match functions for fun, with weekly Patch Notes from decmp.dev.
Start here
Section titled “Start here”What is a decomp?Matching versus non-matching, and why byte-identical output is the goal.
Stay legalNo ROMs, no assets, no leaked code in your repository.
Choose a gameWhat makes a first project friendly, and what makes it hard.
PrerequisitesThe C, assembly and tooling you need before your first match.
Paths by console
Section titled “Paths by console”GameCube and WiiPowerPC, CodeWarrior, decomp-toolkit and objdiff.
Nintendo 64MIPS, IDO and GCC.
GBA and DSARM and Thumb: agbcc on GBA, CodeWarrior for ARM on DS.
PS1 and PS2MIPS on both; old GCC versions and maspsx on PS1.
Switch and 3DSARM64 on Switch, ARM on 3DS, and much bigger binaries.
Match, measure, share
Section titled “Match, measure, share”Track your progress
Upload your objdiff report from CI and get a project page and badges. Set up the action.