fix: restore 43U DOL hash on main #213
Reference in New Issue
Block a user
Delete Branch "agent/restore0928/dol-hash"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
main hasnt actually built the right dol for a while, a clean build of
75c7a24cgives0c106821…instead of26116613…. the fork pointf8d83e5fstill matches, so a bunch of merges since then got through without a real hash check. objdiff scores by symbol name so it never caught any of thiswhat was broken and whats fixed here
-Cpp_exceptions onback on for them.commentsection, the dtk split ones dont), so labs/itoa/strpbrk/strspn/strcspn/atol and a few data syms were getting dropped. addedforce_activein config.yml plus aFORCEACTIVE { $FORCEACTIVE }block in the ldscript templategui::EventHandlernovtable and rewroteHermiteIntpfor EVERY unit, not just channelTitle. thats now all behindIPL_CHANNEL_TITLE_NOVTABLE, which puts the missing 0x18 vtables back in a ton of scene unitscreateNewRecordgoes back tou16 addrType(thats the original mangled name, the enum version was 4 bytes longer)gates (fresh orchestrator build)
rm -rf build/43U && python3 configure.py --version 43U && ninja build/43U/okpassesbuild/43U/main.dolsha126116613f624061ba99c8d1a299aaa6efa85670d,cmpagainstorig/43U/00000008.appis byte identicalninjapasses