Skip to content
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

End the indirect jump when potential hotspot is detected #371

Merged
merged 1 commit into from
Mar 7, 2024

Commits on Mar 7, 2024

  1. End the indirect jump when potential hotspot is detected

    Currently, the indirect jump does not switch to T1C when potential
    hotspot is detected, it would make execution stuck in interpreter mode.
    This revision ensures the execution halts upon identifying a potential
    hotspot. It aims to make the execution process more efficient by
    stopping when a significant area of code usage is detected, allowing
    for targeted optimization.
    qwe661234 committed Mar 7, 2024
    1 Configuration menu
    Copy the full SHA
    6ecc87d View commit details
    Browse the repository at this point in the history