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

PPCAnalyst: Rework the store-safe logic #9486

Merged
merged 1 commit into from Mar 24, 2021

Conversation

JosJuice
Copy link
Member

@JosJuice JosJuice commented Feb 2, 2021

The output of instructions like fabsx and ps_sel is store-safe if and only if the relevant inputs are. The old code was always marking the output as store-safe if the output was a single, and never otherwise.

Also, the old code was treating the output of psq_l/psq_lu as store-safe, which seems incorrect (if dequantization is disabled).

Split out from PR #9458 because this affects the x64 JIT.

@JMC47
Copy link
Contributor

JMC47 commented Mar 3, 2021

Is there anything I can test on this in order to verify it's working?

@JosJuice
Copy link
Member Author

JosJuice commented Mar 3, 2021

I don't know of anything in particular that would be prone to breaking. Just test some games briefly and see if they work fine I guess?

Testing must be done on the x64 JIT.

Copy link
Member

@degasus degasus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tiny change request, else this pull request LGTM.

The output of instructions like fabsx and ps_sel is store-safe
if and only if the relevant inputs are. The old code was always
marking the output as store-safe if the output was a single,
and never otherwise.

Also, the old code was treating the output of psq_l/psq_lu as
store-safe, which seems incorrect (if dequantization is disabled).
@degasus degasus merged commit 75f8ce1 into dolphin-emu:master Mar 24, 2021
10 checks passed
@JosJuice JosJuice deleted the storesafe branch March 24, 2021 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants