From ebd4d215df53ce85c6a0232e4cd3b1ee903f8409 Mon Sep 17 00:00:00 2001
From: Basilisk-Dev <basiliskdev@protonmail.com>
Date: Thu, 23 Apr 2026 22:04:40 -0400
Subject: [PATCH] Issue #3049 - Disable wasm signal handlers on loongarch64

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

diff --git a/js/src/wasm/WasmSignalHandlers.cpp b/js/src/wasm/WasmSignalHandlers.cpp
index 733ad48f99..37afea41de 100644
--- a/js/src/wasm/WasmSignalHandlers.cpp
+++ b/js/src/wasm/WasmSignalHandlers.cpp
@@ -1358,6 +1358,13 @@ ProcessHasSignalHandlers()
 # endif
 #endif
 
+#if defined(JS_CODEGEN_LOONGARCH64)
+    // The loongarch64 port is baseline-only for now: no wasm compiler support
+    // and no Ion interrupt machinery that depends on these process-wide
+    // signal handlers. Keeping them installed risks misrouting ordinary faults.
+    return false;
+#endif
+
     // The interrupt handler allows the main thread to be paused from another
     // thread (see InterruptRunningJitCode).
 #if defined(XP_WIN)