summaryrefslogtreecommitdiff
path: root/vm.c
diff options
context:
space:
mode:
authorTakashi Kokubun <takashikkbn@gmail.com>2023-08-04 15:39:01 -0700
committerTakashi Kokubun <takashikkbn@gmail.com>2023-08-04 15:39:02 -0700
commite80752f9bbc5228dba3066cd95a81e2e496bd9d7 (patch)
treeee3c93a88174e6b8d14c4c59006cbf339aadc717 /vm.c
parent8d7861e3daf64e0bd30b2f9fe56f94eadfde5d3f (diff)
Skip calling jit_exec on Wasm
We often break Wasm build when we modify how jit_exec works. I'm planning to modify it again soon. We actually don't support running Ruby JIT on Wasm, so it doesn't seem worth the maintenance effort.
Diffstat (limited to 'vm.c')
-rw-r--r--vm.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/vm.c b/vm.c
index f67bd30bdd..cd6e3e0b5c 100644
--- a/vm.c
+++ b/vm.c
@@ -2336,9 +2336,7 @@ vm_exec_bottom_main(void *context)
struct rb_vm_exec_context *ctx = (struct rb_vm_exec_context *)context;
ctx->state = TAG_NONE;
- if (UNDEF_P(ctx->result = jit_exec(ctx->ec))) {
- ctx->result = vm_exec_core(ctx->ec);
- }
+ ctx->result = vm_exec_core(ctx->ec);
vm_exec_enter_vm_loop(ctx->ec, ctx, ctx->tag, true);
}