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
If you use an indirect addressing mode with byte size index register, the web site (68kcounter.grahambates.com) calculates an incorrect size and number of cycles - this addressing mode doesn't exist on m68k.
The text was updated successfully, but these errors were encountered:
Hey, sorry I forgot about this and just looking at it now!
What's happening here is that while the actual rule for indirect addressing does only match .w and .l, this is matching the rule for an absolute longword address.
Thinking back, I deliberately made this the default for anything that doesn't match any other known pattern. The idea was that rather than trying to parse and interpret any combination of characters that could potentially form an expression, at this point it can only be something that equates to a number. This does have the unintended effect of silently swallowing errors, but my thinking was that it's not really the job of this tool to validate your syntax. There's likely a whole bunch of stuff that the regular expression based parsing accepts that isn't valid m68k.
I might rethink this in the future if I introduce more accurate parsing that can give useful errors.
If you use an indirect addressing mode with byte size index register, the web site (68kcounter.grahambates.com) calculates an incorrect size and number of cycles - this addressing mode doesn't exist on m68k.
The text was updated successfully, but these errors were encountered: