wasm: Don't use a new AbstractMachine to instantiate modules
Some checks are pending
CI / macOS, arm64, Sanitizer, Clang (push) Waiting to run
CI / Linux, x86_64, Fuzzers, Clang (push) Waiting to run
CI / Linux, x86_64, Sanitizer, GNU (push) Waiting to run
CI / Linux, x86_64, Sanitizer, Clang (push) Waiting to run
Package the js repl as a binary artifact / Linux, arm64 (push) Waiting to run
Package the js repl as a binary artifact / macOS, arm64 (push) Waiting to run
Package the js repl as a binary artifact / Linux, x86_64 (push) Waiting to run
Run test262 and test-wasm / run_and_update_results (push) Waiting to run
Lint Code / lint (push) Waiting to run
Label PRs with merge conflicts / auto-labeler (push) Waiting to run
Push notes / build (push) Waiting to run

Bad rebase conflict resolution broke code, grug sad.
This commit is contained in:
Ali Mohammad Pur 2025-08-26 17:26:04 +02:00 committed by Jelle Raaijmakers
commit bf3fa13773
Notes: github-actions[bot] 2025-08-26 17:08:03 +00:00

View file

@ -579,7 +579,6 @@ ErrorOr<int> ladybird_main(Main::Arguments arguments)
}
if (attempt_instantiate || print_compiled) {
Wasm::AbstractMachine machine;
#if !defined(AK_OS_WINDOWS)
Optional<Wasm::Wasi::Implementation> wasi_impl;