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

Add option around FX1E behaviour #28

Open
jon-axon opened this issue Mar 23, 2023 · 0 comments
Open

Add option around FX1E behaviour #28

jon-axon opened this issue Mar 23, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@jon-axon
Copy link
Owner

There appear to be two different behaviour in the wild for FX1E, which are mutually exclusive, yet there are examples of ROMs that require each of these to run correctly.

Apparently the original COSMAC did not alter vF during execution of this instruction, but some later interpreters set vF to either 1 or 0 depending on whether I overflows beyond normal addressable memory during the operation.

The game Spacefight 2091! relies on the latter behaviour to function correctly, however the demo Sens8tion relies on the former.

I have not seen this behaviour implemented as an option/quirk in any other interpreter, consequently other common interpreters e.g. Octo seem to only handle one form or the other (e.g. Octo doesn't render Spacefight 2091! correctly). It would be nice to implement and surface this as a configurable compatibility option in Chipolata, to allow user mandate of either behaviour.

@jon-axon jon-axon added the enhancement New feature or request label Mar 23, 2023
@jon-axon jon-axon assigned jon-axon and unassigned jon-axon Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant