Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix unimplemented instruction cycles #23

Merged
merged 1 commit into from
Apr 28, 2016

Conversation

marhel
Copy link
Contributor

@marhel marhel commented Apr 27, 2016

According to the M68000UM, the two unimplemented instruction exceptions
both cost 34 cycles, not 4.

Actually, that's a bit of a lie. Table 8-14. Exception Processing
Execution Times does not even mention unimplemented instruction
exceptions, but section 6.3.6 Illegal and Unimplemented Instructions
basically says that unimplemented instructions are just a special case
of illegal instructions in that they have separate exception vectors.

According to the M68000UM, the two unimplemented instruction exceptions
both cost 34 cycles, not 4.

Actually, that's a bit of a lie. Table 8-14. Exception Processing
Execution Times does not even mention unimplemented instruction
exceptions, but section 6.3.6 Illegal and Unimplemented Instructions
basically says that unimplemented instructions are just a special case
of illegal instructions in that they have separate exception vectors.
@kstenerud kstenerud merged commit 15a51d1 into kstenerud:master Apr 28, 2016
marhel added a commit to marhel/r68k that referenced this pull request Apr 28, 2016
This version integrates the following exception related Musashi PRs;

* Fix address error cycle count and cycle depletion behavior
  (kstenerud/Musashi#20)
* Undo instruction cycles in trap exception
  (kstenerud/Musashi#21)
* Undo instruction cycles in trap#n exception
  (kstenerud/Musashi#22)
* Fix unimplemented instruction cycles
  (kstenerud/Musashi#23)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants