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
Cleanup usage of atomic/threadsafe functions #1987
Conversation
|
Why was PowerPCState::Exceptions using atomics anyway? |
|
Looks like 8d6f984 changed PowerPCState::Exceptions... some sort of misguided attempt to fix dual-core. These days, we use ScheduleEvent_Threadsafe when the GPU thread needs to asynchronously cause an interrupt. |
8530ba8
to
96f5498
Compare
|
Thanks for spotting that; fixed. |
|
You're welcome |
Accessing any member of ppcState from a thread other than the CPU thread is not allowed; don't pretend that there's any exception to that rule.
96f5498
to
30d15b3
Compare
|
Ping. |
|
Looks good to me. |
Cleanup usage of atomic/threadsafe functions
|
I am getting this issue every time i close a game in dolphin after this merge: |
|
Yes, please; include your full configuration, and assign it to me. |
|
On my system this merge has caused a 10% speed slowdown |
|
Does PR #2038 help the regression any? |
|
Since it's not merged and there's no build to try, at the moment I am not able to tell... |
|
Unfortunately it doesn't help... |
|
Okay, then I'm not sure what's going on. Please file an issue report. |
We shouldn't use atomic/threadsafe functions when they aren't necessary; it's misleading at best.