-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
SPU2: Optimize reverb resampling #10134
SPU2: Optimize reverb resampling #10134
Conversation
b558523
to
76fd2c5
Compare
Using GSVector seems out of place currently since it's for GS only. What we could do is move it to common and rename it to Vector only or something like that. That way it can be used anywhere. |
FYI, The AVX2 paths will have no effect in the CI/Releases builds, unless you do the whole function-pointer+Multi-ISA thing. As for the name, eh, I'm so used to using GSVector that I think renaming it would actually be a detriment. |
Going to try to set up the multi-isa thing. |
40aa352
to
c853d9d
Compare
bfac162
to
fa4501a
Compare
fa4501a
to
bcdabde
Compare
bcdabde
to
0b35a98
Compare
Description of Changes
Use SIMD for resampling.
Rationale behind Changes
Vroom vroom.
Suggested Testing Steps
Check that things sound the same.
Ok so this is probably a marginal improvement TBH. But I was bored enough to muck around with it. I'll use this opportunity to see what you guys think about using GSVector in the SPU :^)