From 6c8aa85b8b578db03a8c5f0dc0b7e80605592d45 Mon Sep 17 00:00:00 2001 From: fusion32 Date: Mon, 30 Jun 2025 19:23:09 -0300 Subject: `writer.cc` --- TODO.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'TODO.md') diff --git a/TODO.md b/TODO.md index bc73f14..baf6a18 100644 --- a/TODO.md +++ b/TODO.md @@ -1,8 +1,7 @@ ## TODO NEXT -- QUERY.CC - READER.CC -- WRITER.CC - DBFUNCS.CC +- QUERY.CC - Include `x == 0xFFFF` inside `CheckVisibility`? - The map container uses type id zero but it seems to also be used as a "no type" @@ -21,7 +20,7 @@ instead of relying on `NARRAY`. ## Stack allocations -Any functions that use `alloca` or some other form of dynamic stack allocations will cause decompiled functions to be an absolute mess. It usually shows up in the decompiled code as both a size computation like `-(VAR + CONST & 0xfffffff0)`, followed by some assignment. It doesn't make total sense without looking at the disassembly. I've encountered ~30 such computations and expect the functions containing them to be amongt the most challenging/annoying to be properly decompiled. +Any functions that use `alloca` or some other form of dynamic stack allocations will cause it to be an absolute mess. It usually shows up in the decompiled code as both a size computation like `-(VAR + CONST & 0xfffffff0)`, followed by some assignment. It doesn't make total sense without looking at the disassembly. I've encountered ~30 such computations and expect the functions containing them to be amongt the most challenging/annoying to be properly decompiled. ## Exceptions It's absolute hell. -- cgit v1.2.3