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 now detects internal branches better #371
Conversation
For example: ``` addr opcode disasm 80026584 48000054 b ->0x800265D8 ```
|
@dolphin-emu-bot rebuild |
|
LGTM |
|
Does this fix something specific you were looking at? It seems like it runs the risk of being too greedy and clumping external branches into the function being analyzed...breaking the purpose of |
|
Jumping into a random block in another function is not exactly common practice. It was this sequence in specific, where the labels mark the function boundaries as detected without this change in it (see the *'s for the relevant branches): |
|
It's likely to happen on tail calls and no-return code sequences (and shared function chunks, but I don't think it's common in gc-compiler-land). However the current implementation doesn't really protect against this anyways. |
PPCAnalyst now detects internal branches better
|
This commit is causing abnormally long boot times in games. Could we get a fix, or if it will take a while, a revert until it's fixed. It's a bit ridiculous to be waiting nearly 20 seconds for game to start. |
For example: