zasm: fix nasty (iy+d) misparsing bug

*sob*...
This commit is contained in:
Virgil Dupras 2019-07-23 13:58:18 -04:00
parent b95f4c8c24
commit cdb206b7a5
4 changed files with 8 additions and 0 deletions

View File

@ -180,6 +180,7 @@ parseArg:
; note: the "-" part isn't supported yet. ; note: the "-" part isn't supported yet.
inc hl ; (HL) now points to X or Y inc hl ; (HL) now points to X or Y
ld a, (hl) ld a, (hl)
call upcase
inc hl ; advance HL to the number part inc hl ; advance HL to the number part
inc hl ; this is the number inc hl ; this is the number
cp 'Y' cp 'Y'

Binary file not shown.

View File

@ -0,0 +1,6 @@
; There was a very nasty bug (cost me a couple of hours of mis-debugging) where
; ld r, (iy+d) would use the 0xdd byte code instead of the correct 0xfd one.
; genallinstrs didn't catch it because it outputs uppercase. Oh sweet mother,
; how much time did I lose over this...
ld h, (iy+1)

View File

@ -0,0 +1 @@
<EFBFBD>f