Commit ad0a4025 authored by Kunshan Wang's avatar Kunshan Wang

Fixed description of push_frame

parent e4f2ed7e
......@@ -377,12 +377,12 @@ Popping native frames has implementation-defined behaviour. It has undefined
behaviour if a frame is popped but there are frame cursors referring to that
frame.
The ``push_frame`` API function takes a ``stackref`` and a ``funcref`` as
arguments. It creates a new frame on the top of the stack, using the current
version (as seen by the current thread) of the given function. The resumption
point is the beginning of the function version. The return types of the function
must match the *Ts* of the state of the previous frame, which must be
**READY<Ts>**.
The ``push_frame`` API function takes a ``framecursorref`` and a ``funcref`` as
arguments. It pops all frames above the current frame pointed by the frame
cursor, and pushes a new frame for the current version (as seen by the current
thread) of the given function. The resumption point is the beginning of the
function version. The return types of the function must match the *Ts* of the
state of the previous frame, which must be **READY<Ts>**.
There are equivalent common instructions in the IR, too.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment