-
Notifications
You must be signed in to change notification settings - Fork 257
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
__clear_cache fix for ARM 64 devices plus ANDROID cleanup #618
Conversation
8149314
to
6bedec0
Compare
Well I don't like intrinsics but I guess I won't ask you to write it in assembly ;-) |
Feel free to rewrite it in assembly :-) |
Maybe later |
Ok to merge then? |
Yep |
@Gillou68310 I'm getting a warning from static analysis with clang tidy (It was added on Android Studio 3.3):
It may explain all the breakpoint crashes I have been seeing in the play store. This is in the |
That uninitialized variable is bad and should be fixed but I don't think it's the cause of the breakpoint. Currently SWL/SWR/SDL/SDR instructions have no fallback to interpreted opcode, which means that a store with no valid TLB map or an address outside RDRAM (eg: 0xa4000000) will trigger a breakpoint. This is true for all platform except ARM which has no breakpoint. We really need to find the game that triggers this so I can implement interpreted fallback properly. |
Also, I'm still seeing some of these crashes with bad core dumps in arm64 devices:
Any chance we are emitting some bad instruction? I'm not seeing it in arm32. |
that's possible indeed |
Too bad I can't find which game |
¯_(ツ)_/¯ |
This implements a fix for a bug in some arm 64 bit CPUs as seen here:
dolphin-emu/dolphin#4204
Also, removed some ANDROID specific code that is no longer needed.
@Gillou68310 you should review this please. I didn't see any performance penalties.
Should we attribute the source of the fix in the code?