Allow extensions to set the vectorcall field on instances of PyFunctionObject

[itamaro]

BPO	46893
Nosy	@carljm, @DinoV, @itamaro

^{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 = None
closed_at = None
created_at = <Date 2022-03-01.22:14:02.858>
labels = ['interpreter-core', 'type-feature', '3.11']
title = 'Allow extensions to set the vectorcall field on instances of PyFunctionObject'
updated_at = <Date 2022-03-01.22:14:02.858>
user = 'https://github.com/itamaro'

bugs.python.org fields:

activity = <Date 2022-03-01.22:14:02.858>
actor = 'itamaro'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2022-03-01.22:14:02.858>
creator = 'itamaro'
dependencies = []
files = []
hgrepos = []
issue_num = 46893
keywords = []
message_count = 1.0
messages = ['414302']
nosy_count = 3.0
nosy_names = ['carljm', 'dino.viehland', 'itamaro']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46893'
versions = ['Python 3.11']

[itamaro]

CPython extensions providing optimized execution of Python bytecode (like Cinder JIT and Pyjion)
can benefit from being able to modify the vectorcall field on instances of PyFunctionObject to allow calling the optimized path (e.g. JIT-compiled) directly.

We propose adding an API to allow extensions to override this field:

void PyFunction_SetVectorcall(PyFunctionObject *func, vectorcallfunc vectorcall);

[gvanrossum]

@markshannon @itamaro

[itamaro]

this is now targeting 3.12 - how can I update the labels?

GH-92257 adds this API and should be ready for review!

[gvanrossum]

Moved the labels for you, and started the tests running on the PR. Others will have to review it.