Skip to content

bpo-45256: Remove the usage of the C stack in Python to Python calls #28488

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pablogsal merged 17 commits into from
Oct 9, 2021
Merged

bpo-45256: Remove the usage of the C stack in Python to Python calls #28488

Changes from 1 commit
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
8a88fd3
Remove the usage of the cstack in Python to Python calls
pablogsal Sep 17, 2021
799e366
Fix gdb
pablogsal Sep 17, 2021
306e29f
Move depth to frame structure for easier retrieval in debugging tools
pablogsal Sep 17, 2021
fc36be1
Refactor and simplifications
pablogsal Sep 17, 2021
e1091e0
Fix existing bug in the PREDICT() macro for the codepath without comp…
pablogsal Sep 21, 2021
d7a99c1
Apply suggestions from code review
pablogsal Sep 21, 2021
0721cea
Tracing of Python functions is handled at entry not call.
markshannon Sep 23, 2021
a2c0994
Inline creation of coroutines.
markshannon Sep 23, 2021
832bccf
Merge remote-tracking branch 'upstream/main' into simple_cframe
pablogsal Sep 23, 2021
9a63ee1
Reorder flow in CALL_FUNCTION to make it a bit clearer.
markshannon Sep 23, 2021
919b741
Merge pull request #16 from markshannon/simple_cframe
pablogsal Sep 23, 2021
9210541
Update Python/ceval.c
pablogsal Sep 23, 2021
9ce9e63
Fix reference counting when creating a new interpreter frame fails.
markshannon Sep 24, 2021
9a0ceab
Remove _PyEval_FrameFromPyFunctionAndArgs forwarding function.
markshannon Sep 24, 2021
65219b2
Merge pull request #17 from markshannon/simple_cframe
pablogsal Sep 24, 2021
1de88f6
Fix reference leaks (needs cleanup)
pablogsal Sep 29, 2021
f313e8c
Merge branch 'main' into simple_cframe
pablogsal Oct 7, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix existing bug in the PREDICT() macro for the codepath without comp… 
…uted gotos
  • Loading branch information
@pablogsal
pablogsal committed Sep 21, 2021
commit e1091e0e747a531364545c931b16bc6c3b28d0fc
11 changes: 5 additions & 6 deletions Python/ceval.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1372,6 +1372,7 @@ eval_frame_handle_pending(PyThreadState *tstate)
opcode = _Py_OPCODE(word); \
if (opcode == op) { \
oparg = _Py_OPARG(word); \
frame->f_lasti = INSTR_OFFSET(); \
next_instr++; \
goto PREDICT_ID(op); \
} \
Expand Down Expand Up @@ -1615,12 +1616,10 @@ _PyEval_EvalFrameDefault(PyThreadState *tstate, InterpreterFrame *frame, int thr
multiple values.

When the PREDICT() macros are enabled, some opcode pairs follow in
direct succession without updating frame->f_lasti. A successful
prediction effectively links the two codes together as if they
were a single new opcode; accordingly,frame->f_lasti will point to
the first code in the pair (for instance, GET_ITER followed by
FOR_ITER is effectively a single opcode and frame->f_lasti will point
to the beginning of the combined pair.)
direct succession. A successful prediction effectively links the two
codes together as if they were a single new opcode, but the value
of frame->f_lasti is correctly updated so potential inlined calls
or lookups of frame->f_lasti are aways correct when the macros are used.
*/
assert(frame->f_lasti >= -1);
_Py_CODEUNIT *next_instr = first_instr + frame->f_lasti + 1;
Expand Down