11 Commits

Author SHA1 Message Date
1acc5e35e9 chore: move util.zig 2022-10-21 05:13:02 -03:00
7cad3aca13 fix: Detect FRAM ROMs 2022-10-21 05:13:01 -03:00
2bbc12cd1a chore: improve util and Gui API 2022-10-21 05:13:01 -03:00
c34752ac65 feat: auto-detect RTC in commercial ROMS 2022-10-21 05:13:00 -03:00
f2b27f31f4 chore: better conform to zig idioms 2022-10-21 05:12:57 -03:00
4cf58f1faa chore: improve init/deinit methods 2022-10-21 05:12:56 -03:00
1a56f957c1 chore: reorganize some code 2022-10-21 05:12:56 -03:00
1a4a2a56a3 chore: pass the allocator as an argument more often
As of right now, I think the only cases where I shouldn't explicitly pass an allocator
are in read/write functions and deinits
2022-10-21 05:12:56 -03:00
c701156ce6 fix: resolve use-afer-free in backup.zig
This worked fine on stage1, and works fine in debug in stage3.
However, stage3 ReleaseSafe would panic due to what I assume must
have been an undefined behaviour optimization.

While I'm happy that I was quickly made aware of the issue thanks to
the safety checks in ReleaseSafe I do wish that this issue showed itself
in Debug, since I *am* using the GPA
2022-10-21 05:12:56 -03:00
7488fd7fd5 fix: reimpl debug reads w/out throwing away *const Self 2022-10-21 05:12:55 -03:00
91c94fe528 chore: change directory structure 2022-10-21 05:12:54 -03:00