[patch] Patch to disable JIT-specific signal handling when there is no JIT

nojit.patch (text/plain), 1.02 KB, created by Marcus Comstedt on 2022-04-02 10:38:02 UTC

From bdd6d60f76aa7a6c0bdbc2a190bb8c9493cd6e2d Mon Sep 17 00:00:00 2001
From: Marcus Comstedt <[e-mail]>
Date: Sat, 2 Apr 2022 11:59:41 +0200
Subject: [PATCH] Don't use JIT signal handlers if no JIT

---
 js/src/wasm/WasmSignalHandlers.cpp | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/js/src/wasm/WasmSignalHandlers.cpp b/js/src/wasm/WasmSignalHandlers.cpp
index b14d47346..aaac36f2e 100644
--- a/js/src/wasm/WasmSignalHandlers.cpp
+++ b/js/src/wasm/WasmSignalHandlers.cpp
@@ -1652,6 +1652,8 @@ ProcessHasSignalHandlers()
 bool
 wasm::EnsureSignalHandlers(JSContext* cx)
 {
+#ifndef JS_CODEGEN_NONE
+
     // Nothing to do if the platform doesn't support it.
     if (!ProcessHasSignalHandlers())
         return true;
@@ -1660,6 +1662,8 @@ wasm::EnsureSignalHandlers(JSContext* cx)
     // On OSX, each JSContext which runs wasm gets its own handler thread.
     if (!cx->wasmMachExceptionHandler.installed() && !cx->wasmMachExceptionHandler.install(cx))
         return false;
+#endif
+
 #endif
 
     return true;
-- 
2.35.1