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
JitArm64: Make fcmpX with flush-to-zero enabled less bad #9751
Conversation
21fa6f9
to
1cf52c1
Compare
ad4d7ce
to
0ee3831
Compare
| // Setting AH = 1, FZ = 1, FIZ = 0 emulates the GC/Wii CPU's "non-IEEE mode". Unfortunately, | ||
| // the AH and FIZ bits were not added until 2020, so we can't count on setting AH actually | ||
| // doing anything. But flushing both inputs and outputs seems to cause less problems than | ||
| // flushing nothing, so let's just set FZ and AH and roll with whatever behavior we get. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this change in the near future? I'm confused about the relevance of the year.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the future, CPUs will be released which support the AH bit. So for each year that passes, the percentage of users that have a CPU with support for it will increase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I should clarify that "added in 2020" means added to AArch64, not to Dolphin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reworded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, so it's a hardware limitation, not of drivers or AArch itself. Got it
Only tested on a CPU which does not support FEAT_AFP.
See the added code comment for details. Fixes Pokémon Battle Revolution not progressing past the title screen.
0ee3831
to
b6cc3c4
Compare
See the added code comment for details. Fixes Pokémon Battle Revolution not progressing past the title screen.