-
Notifications
You must be signed in to change notification settings - Fork 7
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
Question about M68K_EMULATE_ADDRESS_ERROR #28
Comments
If I disable M68K_EMULATE_ADDRESS_ERROR, vAmiga runs at 75 MHz in warp mode 😎. |
dirk, you better fasten your seat belt now.... |
Amazing, I had the same beer yesterday 😅. It's really delicious, but I wonder what the brewery's putting in there. If I drink more than one, I get a hangover. |
My friend calls the Dunkle Weissbiers “Hangover Juice”! I love them 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've did some performance profiling with vAmiga and found out that 80% of total computation time is consumed by Musashi 😳.
65% is consumed by setJmp() which is called if M68K_EMULATE_ADDRESS_ERROR is enabled. I've seen that Omega also has this option enabled. Did you experience a similar issue? If not, there must be something terribly wrong with me system settings.
The text was updated successfully, but these errors were encountered: