Skip to content

JIT should abandon rest of trace if we cannot optimize it #146297

@Fidget-Spinner

Description

@Fidget-Spinner

Feature or enhancement

Proposal:

The JIT optimizer is now powerful enough that with it on, it pays for the JIT.

However, we seem to still be running code without optimizations. Specifically, when we hit out of space in the JIT optimizer, we just execute the unoptimized code. This is probably pretty bad for performance.

We should stop the trace at the last "safe" point, and _EXIT_TRACE there to allow the trace to grow naturally.

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Linked PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    interpreter-core(Objects, Python, Grammar, and Parser dirs)topic-JITtype-featureA feature request or enhancement

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions