Skip to content

Move Tier 2 interpreter out of _PyEval_EvalFrameDefault #116970

Open

Description

@gvanrossum

See discussion starting here: faster-cpython/ideas#631 (comment)

Basically, we see no real perf improvement for having the two switches inside the same function, and we have some indication that on Windows the compiler is failing to optimize this giant function. In addition, the logic for each of the interpreters is somewhat complicated due to sharing variables and labels.

This is not as simple as reverting gh-111428 (issue gh-111520), but in the abstract, that's the proposal.

The priority isn't clear, but it's probably doing before the 3.13 feature freeze.

Activity

  1. self-assigned this
    on Mar 18, 2024
  2. removed their assignment
    on Mar 20, 2024
  3. gvanrossum commented on Apr 29, 2024

    @gvanrossum
    MemberAuthor

    This will probably be superseded by issue gh-118335 and its PR (gh-118339).

  4. gvanrossum commented on Apr 30, 2024

    @gvanrossum
    MemberAuthor

    This will probably be superseded by issue gh-118335 and its PR (gh-118339).

    (Not really, when configured the Tier 2 interpreter will still co-habitate with the Tier 1 interpreter. But it's unclear if it matters, and we may dust it off later.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    interpreter-core(Objects, Python, Grammar, and Parser dirs)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions