Aliaksandr Kalenik 865e651a7d LibJS: Merge CallFrame into ExecutionContext ... Before this change both ExecutionContext and CallFrame were created before executing function/module/script with a couple exceptions: - executable created for default function argument evaluation has to run in function's execution context. - `execute_ast_node()` where executable compiled for ASTNode has to be executed in running execution context. This change moves all members previously owned by CallFrame into ExecutionContext, and makes two exceptions where an executable that does not have a corresponding execution context saves and restores registers before running. Now, all execution state lives in a single entity, which makes it a bit easier to reason about and opens opportunities for optimizations, such as moving registers and local variables into a single array.		2024-05-02 07:26:13 +02:00
..
BlockAllocator.cpp
BlockAllocator.h
Cell.cpp
Cell.h
CellAllocator.cpp	LibJS: Save min and max block addresses in CellAllocator	2024-04-24 11:42:15 +02:00
CellAllocator.h	LibJS: Save min and max block addresses in CellAllocator	2024-04-24 11:42:15 +02:00
ConservativeVector.cpp
ConservativeVector.h
DeferGC.h
GCPtr.h
Handle.cpp
Handle.h
Heap.cpp	LibJS: Merge CallFrame into ExecutionContext	2024-05-02 07:26:13 +02:00
Heap.h
HeapBlock.cpp
HeapBlock.h
HeapFunction.h
HeapRoot.h
Internals.h
MarkedVector.cpp
MarkedVector.h