Skip to content

Faster _EXIT_TRACE via jump patching #140434

@Fidget-Spinner

Description

@Fidget-Spinner

Feature or enhancement

Proposal:

When a trace ends in _EXIT_TRACE instead of JUMP_TO_TOP, it seems to cost a lot more to jump.

We should do like pypy and patch the trace exit to the actual machine code so it's a direct jump.

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Metadata

Metadata

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