2024-05-01 12:05:53 -03:00
|
|
|
#include "Python.h"
|
|
|
|
|
|
|
|
#include "pycore_ceval.h"
|
|
|
|
#include "pycore_frame.h"
|
|
|
|
#include "pycore_jit.h"
|
|
|
|
|
|
|
|
// This is where the calling convention changes, on platforms that require it.
|
|
|
|
// The actual change is patched in while the JIT compiler is being built, in
|
|
|
|
// Tools/jit/_targets.py. On other platforms, this function compiles to nothing.
|
|
|
|
_Py_CODEUNIT *
|
2024-06-26 16:10:43 -03:00
|
|
|
_ENTRY(_PyInterpreterFrame *frame, _PyStackRef *stack_pointer, PyThreadState *tstate)
|
2024-05-01 12:05:53 -03:00
|
|
|
{
|
|
|
|
// This is subtle. The actual trace will return to us once it exits, so we
|
|
|
|
// need to make sure that we stay alive until then. If our trace side-exits
|
|
|
|
// into another trace, and this trace is then invalidated, the code for
|
|
|
|
// *this function* will be freed and we'll crash upon return:
|
|
|
|
PyAPI_DATA(void) _JIT_EXECUTOR;
|
|
|
|
PyObject *executor = (PyObject *)(uintptr_t)&_JIT_EXECUTOR;
|
|
|
|
Py_INCREF(executor);
|
|
|
|
// Note that this is *not* a tail call:
|
|
|
|
PyAPI_DATA(void) _JIT_CONTINUE;
|
|
|
|
_Py_CODEUNIT *target = ((jit_func)&_JIT_CONTINUE)(frame, stack_pointer, tstate);
|
|
|
|
Py_SETREF(tstate->previous_executor, executor);
|
|
|
|
return target;
|
|
|
|
}
|