mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-07-05 00:21:52 +00:00
LibJS: Allocate ExecutionContext memory using alloca() when possible
This should be faster than heap allocation. However, heap allocation is still necessary in some cases, such as with generators and async functions.
This commit is contained in:
parent
5a92929282
commit
a329868c1b
Notes:
github-actions[bot]
2025-04-24 08:32:11 +00:00
Author: https://github.com/kalenikaliaksandr
Commit: a329868c1b
Pull-request: https://github.com/LadybirdBrowser/ladybird/pull/4434
Reviewed-by: https://github.com/alimpfard
10 changed files with 42 additions and 12 deletions
|
@ -102,7 +102,8 @@ JS::Promise* JavaScriptModuleScript::run(PreventErrorReporting)
|
|||
VERIFY(record);
|
||||
|
||||
// NON-STANDARD: To ensure that LibJS can find the module on the stack, we push a new execution context.
|
||||
auto module_execution_context = JS::ExecutionContext::create(0, 0);
|
||||
JS::ExecutionContext* module_execution_context = nullptr;
|
||||
ALLOCATE_EXECUTION_CONTEXT_ON_NATIVE_STACK(module_execution_context, 0, 0);
|
||||
module_execution_context->realm = &realm;
|
||||
module_execution_context->script_or_module = GC::Ref<JS::Module> { *record };
|
||||
vm().push_execution_context(*module_execution_context);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue