You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using direct addressing mode, no bytes seem to be created. I am using ADCA as an example, but the issue seems to affect all direct addressing mode mnemonics.
@icemanind looks like both explicit direct and extended addressing are not being parsed correctly. So similarly:
ORG $1000
START LDA >$FEEE
END START
The problem is that extended and direct addressing are deferred until later on in the assembly process, but no check is there to see if the program listing explicitly uses < or >. I'll implement a fix for that and add some regression tests as well. Thanks for finding that and reporting it!
No problem! This is a fantastic project you started and it works great. Please keep up the great work! Along the same lines, looking at the code, I don't think the SETDP pseudo mnemonic is actually doing anything (other than being recognized as a pseudo-op by the parser). I haven't actually tried it though, so I could be wrong. Again, thanks for the great work on this!
@icemanind Thanks for the kind words! I really appreciate it! A new pull request should go through momentarily with a fix for the direct and extended addressing modes. You are indeed correct about the SETDP pseudo op. It's a recognized mnemonic, but it still needs to be implemented in the assembler. Thanks again!
Describe the bug
When using direct addressing mode, no bytes seem to be created. I am using
ADCA
as an example, but the issue seems to affect all direct addressing mode mnemonics.To Reproduce
Steps to reproduce the behavior:
test.asm
:python assembler.py --print test.asm
Expected behavior
With the print parameter in place, it should produce this output:
Actual behavior
I am getting no byte codes at all:
The text was updated successfully, but these errors were encountered: