Open agatti opened 4 years ago
Weird, will try to reproduce.
Did you remember to mark the io region as volatile in the "Window->Memory Map" window?
@cbuschardt Marking the IO region as volatile lets the decompiler work as intended, indeed. Thanks for the tip.
That said, is it still a bug in the decompiler? Values are written to the IO area, so there are fewer assumptions to be made from the data in question.
Describe the bug The decompiler creates an incorrect instruction flow. Maybe it gets confused by stack manipulation and interrupt control code being interleaved rather than nested.
To Reproduce Steps to reproduce the behavior:
Expected behavior In the decompiled code,
enableMaskableInterrupts
is supposed to appear after the write toDAT_io_00a1
, not right afterdisableMaskableInterrupts
.Screenshots
Attachments
test.bin.gz
Environment (please complete the following information):