mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-08-31 01:44:14 +02:00
Henrik RydgårdandClaude Opus 5
2f5bb829f3
The old one was reverse engineered from a handful of symbols and got the shape of the format wrong - it required a digit right after the kind character, which most real symbols don't have. Measured against a PSP executable that shipped with its symbol table intact, it decoded 238 of 4662 mangled symbols, most of those incorrectly. Worked out properly from that binary, the format turns out to be: __0 <kind> <name...> <params> [_ <return type>] [<qualifier>] where the kind character (member function, free function, operator, data) is the only thing that says how many name components follow, since nothing separates the last one from the first parameter. Lengths are letters (A = 0, a = 26); "5" marks an enclosing namespace; "7...._" is a template argument list, with "4" plus a compact integer for a non-type argument and "9<index>A" for a back-reference to one; "T<index>" and "N<count><index>" repeat an earlier parameter; a trailing "K" is const and a trailing "T" is a static member function. Also handles __TID_/__T_ (the two halves of a class's RTTI) and __sti__ (a translation unit's static initializers). That decodes 4661 of the 4662. The one holdout is an STL symbol whose template argument is a reference to a member of another template. Declarator wrapping is shared with the CodeWarrior demangler now, so pointers to arrays come out as "short (**)[64]" in both. docs/SNSystemsMangling.md describes the format, marking what's inferred rather than attested. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SF5eS5QDNexLksRDeDZvwY