JP (HL) / (IX) / (IY) lifted as a memory-indirect jump
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
For a register-deref target, goto_or_jump() in Z80IL.py runs the operand through operand_to_il() without peel_load=True, so it emits a load:
e9 JP (HL) -> jump([HL].w) # should be jump(HL)
JP (HL) jumps to the address in HL, it does not dereference it. This breaks the standard Z80 jump-table dispatch idiom.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Z80IL.py at goto_or_jump() and trace how the register-deref target is passed to operand_to_il(). Check the JP (HL), JP (IX), and JP (IY) cases, then verify that the lifted output treats each register as the jump target rather than loading from memory. Confirm the standard Z80 jump-table dispatch behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100