-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
VIF: Improve IR setup for skipped unpack inputs/writes #8778
Conversation
68232e0
to
c8c8754
Compare
@@ -263,6 +258,26 @@ void VifUnpackSSE_Dynarec::ModUnpack(int upknum, bool PostOp) | |||
} |
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.
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.
when the error is triggered the value of it is gonna always be 11.
Is that new? That shouldn't have changed |
It is from 2020. https://forums.pcsx2.net/Thread-True-Crime-Streets-of-L-A-SLUS-20550-U--29732?pid=616280#pid616280 |
Then I don't care |
983c611
to
3b07975
Compare
3b07975
to
976aeb0
Compare
Description of Changes
Improved detection of when rows/cols/write protect are used instead of input data, reducing codegen of the VIF JIT
Rationale behind Changes
potentially more brr in some places, but not much.
Suggested Testing Steps
Test games, if it says "Skipping stuff!" in the console, it's hit the new code. Tested Kingdom Hearts 2, Tales of Legendia and Gran Turismo 4 already (the latter two hit it)