Skip to content

Frames should store next_instr instead of lasti #91333

@brandtbucher

Description

@brandtbucher
BPO 47177
Nosy @markshannon, @brandtbucher
PRs
  • bpo-47177: Replace f_lasti with prev_instr #32208
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/brandtbucher'
    closed_at = <Date 2022-04-07.19:32:09.034>
    created_at = <Date 2022-03-31.01:12:26.728>
    labels = ['interpreter-core', '3.11', 'performance']
    title = 'Frames should store next_instr instead of lasti'
    updated_at = <Date 2022-04-07.19:32:09.033>
    user = 'https://github.com/brandtbucher'

    bugs.python.org fields:

    activity = <Date 2022-04-07.19:32:09.033>
    actor = 'brandtbucher'
    assignee = 'brandtbucher'
    closed = True
    closed_date = <Date 2022-04-07.19:32:09.034>
    closer = 'brandtbucher'
    components = ['Interpreter Core']
    creation = <Date 2022-03-31.01:12:26.728>
    creator = 'brandtbucher'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 47177
    keywords = ['patch']
    message_count = 2.0
    messages = ['416409', '416938']
    nosy_count = 2.0
    nosy_names = ['Mark.Shannon', 'brandtbucher']
    pr_nums = ['32208']
    priority = 'normal'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'performance'
    url = 'https://bugs.python.org/issue47177'
    versions = ['Python 3.11']

    Metadata

    Metadata

    Assignees

    Labels

    3.11only security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)performancePerformance or resource usage

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions